On Sat, Aug 08, 2009 at 04:03:38PM +0200, Max Vozeler wrote: > Hi all, > > Attempt to summarize the discussion so far (please correct): > > 1) We should use /dev/mapper/ paths rather than UUID in the fstab > entries for all device mapper devices. > > 2) For some type of device mapper devices (multipath), using the > /dev/disk/by-id/ symlinks would be better than /dev/mapper/. The last point only makes sense if we work on a stable device naming with _and_ without multipath. I think Novell does this with /dev/disk/by-id/scsi-XXXXX-partY. This points to the underlying block device(s) (e.g. /dev/sda1) without multipath and points to /dev/mapper/<wwwid>-partY when turning on multipath.
Looking at /dev/disk/by-uuid/ also seems to do the trick: it points to /dev/sdaY without and to /dev/mapper/<wwid>-partY with multipath. So if we'd use this turning multipath on and off would be transparent to the user. What's the reasoning for using UUID= instead of /dev/disk/by-uuid/ in fstab? Non udev systems? Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org