James C. McPherson wrote: > Gregory Shaw wrote: > >> Hi. I'd like to request a feature be added to zfs. Currently, on >> SAN attached disk, zpool shows up with a big WWN for the disk. If >> ZFS (or the zpool command, in particular) had a text field for >> arbitrary information, it would be possible to add something that >> would indicate what LUN on what array the disk in question might be. >> This would make troubleshooting and general understanding of the >> actual storage layout much simpler, as you'd know something about any >> disks that are encountering problems. >> >> Something like: >> >> zpool status >> pool: local >> state: ONLINE >> scrub: scrub completed with 0 errors on Sun Sep 23 04:16:33 2007 >> config: >> >> NAME STATE READ WRITE CKSUM NOTE >> local ONLINE 0 0 0 >> raidz1 ONLINE 0 0 0 >> c2t0d0 ONLINE 0 0 0 Internal SATA on >> left side >> c2t2d0 ONLINE 0 0 0 Internal SATA on >> right side >> c2t3d0 ONLINE 0 0 0 External SATA disk 1 >> in box on top >> c2t4d0 ONLINE 0 0 0 External SATA disk 2 >> in box on top >> spares >> c2t5d0 AVAIL External SATA disk 3 >> in box on top >> >> errors: No known data errors >> >> >> 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. 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. -Tim _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
