Why not use devlabel? It's a small userspace app which maps symlinks to
underlying disk names. It uses Page83/Page80 data to track the true
locations of disks even if their hd/sd name changes and simply updates the
symlink to point to the right place.
devlabel to do list:
- support multipath configs (if devlabel currently finds the same uuid on 2
disks, it wont let you add a symlink to either)
- utilize sysfs info (rather than using my user apps to get 83/80 info, just
get it from sysfs)
http://www.lerhaupt.com/devlabel
Gary
--- Some compatibility needs more code than other compatibility. The desired compatibility includes the following, much of which has been noted earlier in this thread, and some of which may need to wait for multipath I/O and other of which might be best provided by a volume manager:o It must be possible to switch between 2.4 and 2.5/6 kernels without a given disk's name changing.
o New 2.5/6 installations should se a clean disk naming scheme without historical cruft.
o Removing or adding one disk should not affect the names of other disks. Ideally, moving a given disk from one place to another should not change its name. "The good news is that we repaired your disk. The bad news is that, due to the resulting name changes, your application thoroughly corrupted all of its data."
o Adding or removing a FC or SCSI adapter should not affect the names of disks hanging off of other FC or SCSI controllers. Ideally, the name of a disk should not change when its FC or SCSI controller is moved from one slot to another.
o Failures of or repairs to the FC fabric should not change the names of any of the disks (though a sufficiently thorough failure might make some of the disks unreachable).
o Cluster nodes should ideally have the same name for a given disk. Extra credit, though greatly appreciated by anyone who has ever had to deal with a cluster where different nodes have different names for the same disk. ;-)
Thanx, Paul
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:36 EST