On Sun, 23 Nov 2008 17:02:57 -0600 Tim <[EMAIL PROTECTED]> wrote: > On Sun, Nov 23, 2008 at 4:55 PM, James C. McPherson > <[EMAIL PROTECTED] > > wrote: > > > On Sun, 23 Nov 2008 06:13:51 -0800 (PST) > > Ross <[EMAIL PROTECTED]> wrote: > > > > > I'd also like to know how easy it is to identify drives when you > > > use this card? Is it easy to know which is which after you've > > > had a few failure & swapped drives around? > > > > Hi Ross, > > in general, it's just as easy to identify drives attached to > > this card as it is to identify drives attached to any other > > card. > > > > The output from 'iostat -En' will help, along with careful > > observation of the drive's serial number and devid. You can > > find the devid (which, last I checked, is guaranteed to be > > unique) by looking for the "devid" property associated with > > your specific device. ... > I don't know that that necessarily makes it *EASY* to find the drive, > especially if they're in a hot-swap bay. Something like an "led_on" > type command would be helpful. Whether that be through sending IO to > the drive to light up an activity LED, or through other means.
Right, so you need to have more information available to you from the specific hardware that you've got installed. We've got sestopo ($SRC/cmd/scsi/sestopo) which makes use of libscsi and libses to handle jbods that Sun makes, but for generic hardware it's more difficult. As far as I can tell, there's no non-SCSI Enclosure Services way of turning on an LED on a drive unless you want to muck around with IPMI - see ipmitool(1m). cheers, James -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
