feisty upgrade fstab

[blu-5a1Jt6qxUNc at public.gmane.org (Tom Metro)]

James Kramer wrote:
> I upgraded to Ubuntu feisty
> The upgrade changes the /etc/fstab
> ...I was wondering why the UUID doesn't work.

It appears I ran into the same issue:

mythtv:/etc# rcsdiff -r1.6 -r1.7 fstab
===================================================================
RCS file: RCS/fstab,v
retrieving revision 1.6
retrieving revision 1.7
diff -r1.6 -r1.7
13,14c13,14
< #/dev/video_vg/video_lv
< UUID=vljNR0-0ZAY-5bxB-bb0M-eVY3-hJpL-P2zyA0 /video xfs defaults 0 0
---
 > #UUID=vljNR0-0ZAY-5bxB-bb0M-eVY3-hJpL-P2zyA0
 > /dev/video_vg/video_lv /video xfs defaults 0 0


I logged that change with the message:
Apparently UUID mechanism doesn't work for LVM. Revert.

I didn't bother investigating. I have other file systems mounted via 
UUID and they seem to work.

In my case what is returned from vol_id doesn't match fstab, so that 
seems to be a good explanation. I'd recommend playing around with the 
mount command using the UUID identifier and see what it reports.

A possibly related issue is that when Feisty switched to udev, there 
were race conditions in the start up scripts, which triggered a variety 
of problems, such as mdadm managed RAID arrays not getting fully 
assembled after a reboot (I mentioned that on this list a month or so 
ago). Maybe a scan for file systems based on UUID fails because the 
devices aren't ready yet, but when the mount is actually performed they are.

  -Tom

-- 
Tom Metro
Venture Logic, Newton, MA, USA
"Enterprise solutions through open source."
Professional Profile: http://tmetro.venturelogic.com/

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.