History for this is based on bug 117225. Note that the problem was with
/dev/mapper entries, not /dev/disk/by-uuid entries. Perhaps the
/dev/disk/by-uuid issue is a side-effect of this? (I don't use FS UUIDs
for mounting since /dev/mapper names are already good enough.) I would
be fine with /dev/disk/by-uuid always pointing to the origin -- it makes
sense, as detailed in comment 3.
Associated changelogs:
devmapper (2:1.02.18-1ubuntu4) gutsy; urgency=low
* Fix a regression introduced by Kees's otherwise largely correct patch.
We still need to not run vol_id on snapshot target devices, otherwise
we'll end up using a changing device, and arguing over UUID/LABEL
symlinks. (This might not be a complete fix, LVM may need to be patched
to make inactive devices).
* Correct a school-boy error with the stat()/mknod() loop; we can't unlink
then mknod() since that means there's a period without a device node,
which could upset callers. Instead rename() the new device node over
the top.
-- Scott James Remnant <[email protected]> Tue, 29 May 2007 09:40:24
+0100
devmapper (2:1.02.18-1ubuntu3) gutsy; urgency=low
* Adjust debian/dmsetup.udev rule to not ignore "snapshot" devices. This
will be needed even after "udev-lvm-mdadm-evms-gutsy" is solved (LP:
#117225).
* Update Maintainer fields for Ubuntu.
-- Kees Cook <[email protected]> Sun, 27 May 2007 12:12:22 -0700
--
disk/by-uuid/foo symlink points to snapshot rather than the origin
https://bugs.launchpad.net/bugs/460906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
