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.
Something like a text file? :-P The problem with this is that wrong information is much worse than no information, there is no way to automatically validate the information, and therefore people are involved. If people were reliable, then even a text file would work. If it can't be automatic and reliable, then it isn't worth doing. There have been a number of map-this-to-that implementations over the years, but they have all relied upon intimate knowledge of the hardware which also has fixed physical addressing (eg. SSA, thumper, et.al.) The virtual new world intentionally tries to hide this sort of info. There was a time when everyone on the internet knew the IP addresses of all the cool places. After a week or two, work begun on a name service ;-) Perhaps devices should be name service aware and the protocols extended to perform name lookups. -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
