Q: Let us assume you have dynamic numbering disk0..N as you suggest,
and you have some s/w RAID of SCSI disks. A disk fails, and is (hot)
removed. Life continues. You reboot the machine. Disks are now numbered
disk0..(N-1). If the RAID config specifies using disk0..N thusly, it
is going to be very confused, as stripes will appear in the wrong place.
Doesn't that mean the file specifying the RAID config is going to have
to enumerate SCSI IDs (or something configuration invariant) as
opposed to use the disk0..N numbering anyway? Sure it can interrogate
each disk0..N to see which has the ID that it actually wanted, but
doesn't this rather subvert the purpose?
IE, given one could create /dev/disk/?.+, isn't the important
argument that they share common major device numbers etc., not whether
they linearly reorder precisely to 0..N as opposed to have some form
of identifier guaranteed to be static across reboot & config change.
-- Alex Bligh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/