Yeah, it's not really 'easy', but certainly better than nothing. I would imagine it would be possible to write a script that could link all three drive identifiers, and from there it would relatively simple to create a chart adding the physical location too.
I agree with Tim that we really need a way to identify drives, even a command to manually flash the fault LED would be good. However, I know that on Sun hardware, there's a blue LED that identifies drives as soon as you "cfgadm -c unconfigure" them, so I doubt it's going to be a priority for Sun to add this for other brands of hardware. The way I see it, the best way to manage third party SAS drives it to have a table with the following information. I don't have a SAS controller yet though to test out the idea, does this look sensible? ZFS Drive cfgadm serial physical location (col-row) c0t0d0 sata0/1 3QF0EAFP 1-1 I'm thinking that's an easy enough way to manage a server, and printed serial number stickers on the hot swap bays would be a good way to double check that the correct drive is about to be removed. In fact, if I created a text file linking serial numbers to physical locations, would it be possible to write one script that output all of that? Then identifying a drive would just be a case of grepping that scripts output for whatever information you know. -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
