Stefan /*St0fF*/ Hübner napsal(a):
I cannot quite understand your problem. As every part of the array
contains it's own metadata, it doesn't matter to md which /dev/sdX a
drive is. It might matter a bit for boot-time assembly, but actually
that's what UUIDs are for.
I know how UUIDs work.
My problem with device names is not a "critical", it's about "user
friendliness" of the physical disk management.
If a disk fails and I receive email "A Fail event had been detected on
md device /dev/md2. It could be related to component device /dev/sdd3",
how will I know which disk should be replaced, if the device name is not
fixed/persistent? Is it the disk in the first bay, or the second? Aside
of the solution documented on the wiki page, I could also use try a
simpler one based on the idea here:
http://www.outsidaz.org/blog/2009/11/05/identifying-failed-drives-via-udev-and-mdadm/
But for the disk management purposes, I prefer having the disk names
fixed according the the disk bay position. So disk in bay nr. 1 is
/dev/sda, bay nr. 2 is /dev/sdb, etc.
The wiki page I created is just about this. I haven't found any document
like this anywhere else, so if it helps someone, I'll be glad.
Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
