Thanks for the reply. Detaching a faulty disk from a zpool before physically removing the disk does NOT make much sense as a ZFS appliance.
When ZFS detects a faulty disk, the hot spare kicks in, and the user pulls out the faulty disk, and puts a new disk in, and walk away. In this scenario, "autoreplace" is set to "on", there should be no "drive type unknown" entry left. Is there any way to remove the old entry from format once the faulty disk is replaced ? by generating a new hot-plug event? Tianhong Zhao | Senior Systems Architect p. +1.514.683.1020 x145 [email protected] www.nexsan.com This message is confidential and may also be legally privileged. It is intended for the use of the individual to whom it is addressed. If you are not the intended recipient, please notify the sender via email and delete the message and you should not copy it or use it for any purpose, nor disclose its contents to any other person. Thank you. -----Original Message----- From: Ada [mailto:[email protected]] Sent: Tuesday, May 03, 2011 4:30 AM To: TianHong Zhao Cc: [email protected] Subject: Re: [driver-discuss] drive type unknown It is a normal symptom, when you pull out a faulty zpool disk, zfs has already hold this disk, then hot plug function can not destroy this disk's device node. So it is still in format disk list, but there is no real disk, then "drive type unknown" Ada TianHong Zhao wrote: > > Hi, > > I don't know if this is the right forum, but I think it's driver related. > > I use *mpt_sas* driver to connect my front-bay SAS disks, mpt_sas is > configured to use *MPxIO*. > > *If I pull out a faulty zpool disk, I always have a "drive type > unknown " entry in the output of "format" ,* > > Putting a new disk into the same SAS bay does not remove that entry. > > 0. c1t5000C50028C8B377d0 <SEAGATE-ST3600057SS-0006-558.91GB> > > /scsi_vhci/disk@g5000c50028c8b377 > > 1. c1t5000C50028C89B5Bd0 <drive type unknown> > > /scsi_vhci/disk@g5000c50028c89b5b > > The only way to get rid of this entry is to put the *same* disk back, > or maybe reboot can get rid of this entry, but I haven't tried. > > *However, if I pull out a disk that does not belong to a zpool, I > don't have this entry in "format".* > > I understand that each SAS disk has its own GUID, and when MPxIO is > enabled, Solaris uses > > That GUID as part of the OS path, that explains why putting a new disk > into the bay does not remove the old entry, > > But why removing a disk leaves a entry in format, shouldn't devfsadm > remove that path ? > > Is this a known issue for SAS disk? or Did I miss anything > configuration-wise ? > > How can I remove this entry without reboot ? > > Thanks > > *Tianhong Zhao | *Senior Systems Architect > *p.* +1.514.683.1020 x145 > > [email protected] > > www.nexsan.com <http://www.nexsan.com/> > > Description: cid:[email protected] > > This message is confidential and may also be legally privileged. It is > intended for the use of the individual to whom it is addressed. > > If you are not the intended recipient, please notify the sender via > email and delete the message and you should not copy it or use > > it for any purpose, nor disclose its contents to any other person. > Thank you. > > ---------------------------------------------------------------------- > -- > > _______________________________________________ > driver-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/driver-discuss > _______________________________________________ driver-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/driver-discuss
