Greg Shaw wrote: > James C. McPherson wrote: >> Bill Sommerfeld wrote: >> >>> On Wed, 2007-09-26 at 08:26 +1000, James C. McPherson wrote: >>> >>>> How would you gather that information? >>>> >>> the tools to use would be dependant on the actual storage device in use. >>> luxadm for A5x00 and V8x0 internal storage, sccli for 3xxx, etc., >>> etc., >> >> No consistent interface to use, then, unless another tool >> or cruft gets added to ZFS to make this happen. That would >> seem to defeat one of the major wins of ZFS - storage >> neutrality. >> >> >> > I'd be happy with an arbitrary field that could be assigned via a > command. Intelligence could be added later if appropriate, but at this > point, figuring out what-is-where on a big list of disk IDs on a SAN > device is very difficult. > > So, aiming low, a text field that could be assigned. In the future, > perhaps something that would associate a serial number of something > similar to that name?
That sounds like an ok RFE to me. For some of the arrays (eg HDS) that we come into contact with, it's possible to decode the device guid into something meaningful to a human, but that's generally closed information. 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
