|
|||||||||||
|
Re: /dev/disk/by-uuid does not exist
From: Miro Dietiker <miro.dietiker.maillist(at)md-systems.ch>
Date: Mon Nov 26 2007 - 20:03:31 EST
I tested a lot more things with the udev and by-uuid...
Miro Dietiker schrieb:
Since lvm-paths from wrapper are persistent, UUIDs are not needed to
access them.
But: when adding new disks inside a system with conflicting md superblocks (say 2 disks tell to be /dev/md0 raid1 and another 2 disks tell to be /dev/md0 raid1 from an earlyer production...) things go wrong. Possibly ancient disks are mounted as md0 where the newer (possibly original root array) from system is assembled elsewhere. I don't understand why the UUID of the md superblock could be used for accessing the md device and getting some distance from the strict mdX persistency (which could not be guaranteed in any case)... Are there any inputs on this?
What's wrong with the default system setup? How to use UUID of md on boot?! Is it even possible to get uuid in that environment? ThX for all inputs! -- Miro Dietiker -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Mon Nov 26 22:02:45 2007 This archive was generated by hypermail 2.1.8 : Tue Feb 26 2008 - 05:10:32 EST |
||||||||||
|
|||||||||||