severity 493216 important
thanks
On Fri, Aug 01, 2008 at 08:24:38AM -0400, Theodore Tso wrote:
> On Fri, Aug 01, 2008 at 02:13:31PM +0200, Marco d'Itri wrote:
> > On Aug 01, Guido Günther <[EMAIL PROTECTED]> wrote:
> >
> > > Reason is that findfs and friends query /etc/blkid.tab to find the
> > > device matching the UUID. Since blkid.tab has things like
> > > /dev/.static/dev/hda7 (no idea why blkid picked that one in favour of
> > > /dev/hda7) this breaks the mount.
> > I am sorry to hear that blkid has been broken for a long time.
>
> Can you someone explain to me what the heck the /dev/.static/dev/hda7
> hack is all about?
OK, now I know what /dev/.static is, but I still don't get those names
in my /etc/blkid.tab file, and I'm not sure how they got into yours.
It certainly isn't the name which is used by default, so I'm not sure
how they would have gotten into the blkid file at all in the first
place.
All I can think of is that at some point someone accidentally typed
the command blkid /dev/.static/dev/sda7 while running as root, and
this errant got stuck in your /etc/blkid.tab file. I see (and will
fix) the bug which causes blkid to not fix this problem automatically,
but this is something which I've never seen show up in peoples
/etc/blkid.tab files in the normal course of events.
If you run the command the command "blkid -g" as root the errant
/dev/.static entry will go away. "cp /dev/null /etc/blkid.tab" will
also make the problem go away, and I haven't been able to find a way
to make blkid put those names into /etc/blkid.tab unless forced via
explicit human intervention.
Am I right in assuming that udev 0.125 is not something that you guys
are planning on trying to slide into Lenny?
- Ted
P.S. The huge bug with libvolumeid is that it relies on
/dev/disk/by-*, which only gets updated at boot-time. So freshly
created filesystems, swap spaces, etc., won't be foud by libvolumeid
until after you reboot. That is so hugely windows-eque that I'm
amazed users of libvolumeid put up with it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
