On 8/5/07, LaMont Jones <[EMAIL PROTECTED]> wrote: > On Sat, Aug 04, 2007 at 02:43:04PM +0100, James Youngman wrote: > > Everything worked fine 'til I upgraded... > > So, whatever populates /dev/disk/by-label is not aware of (LVM2 & MD), > > and since mount no longer itself supports LABEL= directly, mount fails > > to mopunt perfectly good filesystems. This makes the system unusable. > > The latest mdadm package seems to provide hooks for vol_id to populate > /dev/disk/*. I expect that the latest LVM does as well.. In any case, > it would appear to be a bug in udev or lvm for not populating the table > that libvolume-id is using. Does the lvm2 package in sid fix the issue?
I upgraded to that just now in order to answer your question. It does not fix the issue. ii lvm2 2.02.26-1+b1 The Linux Logical Volume Manager FWIW, fsck still works fine in this configuration; the filesystems can be checked but not mounted. IMO, if we're going to withdraw a feature that people are depending on in order to boot (and I have been depending on it for the past four years), we should really provide people with a warning and some time window in which to change their configuration. James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
