Bug#612402: upgraded systems won't boot from UUID volumes

Henrique de Moraes Holschuh hmh at debian.org
Mon Apr 8 00:43:45 UTC 2013


On Sun, 07 Apr 2013, Ben Hutchings wrote:
> So it seems that this is only going to be an issue if users take the
> unusual step of changing /etc/fstab to refer to LVs by UUID.  But maybe
> there are management tools that do that as a matter of course?

One should never use UUIDs in fstab to refer to non-unique filesystems
(which is pretty much a normal thing with LVM, as the use of snapshotting is
common).  Any management tools that screw this up need a reality check (and
post-haste bug fix).

Doing otherwise is courting a data loss scenario.  We've seen it happen a
large number of times over the years because of the md 0.90 layout, until
userspace tools started to add defensive layers to make it less likely to
happen.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh



More information about the pkg-lvm-maintainers mailing list