Tim Spriggs wrote: > James C. McPherson wrote: >> Gregory Shaw wrote: ... >>> The above would be very useful should a disk fail to identify what >>> device is what. >> How would you gather that information? >> How would you ensure that it stayed accurate in >> a hotplug world? > If it is stored on the device itself it would keep the description with > the same device.
What about when you replace a disk in an array? What process would go and write the appropriate information? How about a bootstrap for this? What would accomplish it? What if you moved your entire system and re-cabled your arrays slightly different? We have the beauty of devids to make sure that the pools still work, but the physical information Greg is talking about would almost certainly be incorrect. > In the case of iSCSI, it would be nice to keep lun info instead of > having to correlate the drive id to the iqn to the lun, especially when > working with luns in one place and drive ids in another. When I was playing around with iscsi a few months back, I used 1gb files on zfs which I then exported.... because I could. What sort of lun info do you want in that sort of use case? "Position" would be quite useless in some respects. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
