Hi Philipp Apologies for not following up earlier.
On Mon, 20 Oct 2008, Philipp Hübner wrote: > I tried, it's definetly not needed. > Furthermore I installed system-config-lvm and lvm2 on a clean > lenny-system: dm_mod get's loaded instantly after the installation, > system-config-lvm works out of the box. > > Then I removed all the dm_-modules manually, and tried again: > system-config-lvm still came up, without problems. > I checked, and after system-config-lvm had reloaded lvm2, the > dm_-modules still weren't loaded. I had a look at this. I installed etch in virtualBox, then upgraded to lenny. The dm_-modules were loaded even before I installed system-config-lvm and lvm2. So something is different between that vm and my desktop. I've had a quick look and nothing stands out as obvious to me. (And I probably won't get around to following that up). > Haven't tried to use system-config-lvm then, as you already told me that > without dm_mod lvcreate etc. don't work. > If I stop lvm and unload dm_mod, system-config-lvm crashes with the same stacktrace as the initial bug report. If I try the same in the vm, system-config-lvm works ok. It allows me to initialise partitions, add them to volume groups, but not to create logical volumes. (When I attempt to create an lv it displays the same error message as lv-create in a message box, but doesn't crash). So again there is something different between my Desktop originally installed pre-etch, and an more recent default install. > So it seams, dm_mod has not caused your crash directly, which is gone > now I assume? Crash is gone, unless I manually unload dm_mod (which counts as user error). Agreed that dm_mod doesn't seem to be the cause of the crash, despite how I can trigger the crash on my desktop. Strange how my desktop and the vm differs. Maybe after years of upgrades I should think about a clean install ;) . Need to move 64-bit eventually. > > The bug you filed against lvm2 could be right though. > Will follow up with similar info there. Thanks for your help. Andrew V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]