Ok, after the anger about a lost day (because an ubuntu kernel update
resulted in a deployment of 5 machines not booting anymore) has settled, let
my try to turn this into some useful bugreport.

2007/9/6, Theodore Ts'o <[EMAIL PROTECTED]>:
>
> Hi, please send the exact steps you used to reproduce this, instead of
> just giving me conclusions.   And please tell me what version of
> Ubuntu/e2fsprogs you were using, thanks.


This is blkid 1.0.0 (12-Feb-2003) on ubuntu 7.04.

When you say "blkid", do you mean the blkid program, or the
> /etc/blkid.tab file?   When you run the /sbin/blkid program, it will
> scan the devices which are currently available and revalidate the
> partitions before printing out the results.

   If the /etc/blkid.tab fle
> is writeable, it will update /etc/blkid.tab with the results.   I have
> tested this by editing /etc/blkid.tab and changing the labels and uuid's
> in /etc/blkid.tab, and then running the /sbin/blkid program, and prints
> the correct results.


Works as advertised. -> User error, thanks for  providing correct usage
information.
The actual problem in this case is not a software bug, but
misleading/incomplete information in ubuntu.


If what you are complaining about is that partition imaging software is
> changing the UUID of the restored partition, but not changing the UUID
> in /etc/fstab, or that when you reformat the swap-space, all possible
> /etc/fstab files aren't getting updated, that's not blkid's problem.
> It's not responsible for the contents of /etc/fstab.  It would be up to
> the partition imaging software to update /etc/fstab, and how to deal
> with the reformating the swap space problem is a hard one, but I would
> submit that's not a common case, and a system administrator who tries to
> install a second Linux system on the same computer is going to have to
> be responsible for editing /etc/fstab on the first installed system.


So as stated above, i would agree that this is no valid bug against blkid or
e2fsprogs in this form, and i'm content  with the bugreport getting
rejected.

So what i'm really complaining about is that the concept of  UUID-based
mounting
in ubuntu after libata was introduced doesn't really work out in reality,
and poses more problems than it solves in many cases.
But being a distro-design problem, not a bug in an individual  package this
has to be taken to the appropriate forum.

-- 
blkid shows outdated / wrong UUID 
https://bugs.launchpad.net/bugs/137314
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to