On Thu, 2006-09-21 at 12:23 -0400, Dave Jones wrote: > On Thu, Sep 21, 2006 at 01:48:06PM +0200, Roy-Magne Mo wrote: > > Dave Jones wrote: > > > Loading dm-snapshot.ko module > > > -Making device-mapper control node > > > -Scanning logical volumes > > > - Reading all physical volumes. This may take a while... > > > - Found volume group "VolGroup00" using metadata type lvm2 > > > -Activating logical volumes > > > - 3 logical volume(s) in volume group "VolGroup00" now active > > > Trying to resume from /dev/VolGroup00/LogVol01 > > > > > > Still seeing this with 2.6.17-1.3001, but I do suspect this is because > > the lvm-utilities is segfaulting during mkinitrd, so the initrd is > > broken - and the kernel itself is ok. > > > > I've registered a BZ for it: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207474 > > > > Does this sound sane? > > Gaaaagrgh. device-mapper. I hates it. Hate hate hate. > This may be the reason a number of people were affected by > this when upgrading from FC4->FC5. I'll release note this > in the next kernel update I push. > > Thanks for your investigation into this. It should be noted that in current mkinitrd we're always using lvm.static . This is as of Sep 1, version 5.1.10-1 . -- Peter -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list