DELL SAS5/E Controller bug

[John Baldwin]

On Wednesday 20 January 2010 4:30:52 am Stephane LAPIE wrote:
> Hello list,
> 
> Basically I'm experiencing the same problem as described here :
> https://forums.freebsd.org/showthread.php?t=9407 (linking for reference)
> 
> Drives disconnections are not recognized instantly, and instead I get
> the following dmesg entries :
> mpt0: mpt_cam_event: 0x16
> mpt0: mpt_cam_event: 0x16
> 
> (Sometimes I also get "mpt0: mpt_cam_event: 0x12" events)
> 
> This is really crippling as this litterally paralyzes the ZFS pool until
> the controller finally comes to its senses (...or until a disk gets
> replugged in, which provokes a flush of all the buffered failed SCSI
> requests).
> 
> Hardware is recognized as :
> mpt0 at pci0:6:8:0:	class=0x010000 card=0x1f041028 chip=0x00541000 rev=0x01
> hdr=0x00
>     vendor = 'LSI Logic (Was: Symbios Logic, NCR)'
>     device = 'SAS 3000 series, 8-port with 1068 -StorPort'
>     class = mass storage
>     subclass = SCSI
> 
> Did anyone else experience this, or find a proper work-around ?

Invoke 'camcontrol rescan' after removing a drive.  mptutil(8) does the 
equivalent when adding and removing volumes to make up for the driver not 
automatically rescanning.

-- 
John Baldwin