From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 03:23:51 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18C671065674 for ; Thu, 28 Apr 2011 03:23:51 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id EE6B48FC19 for ; Thu, 28 Apr 2011 03:23:50 +0000 (UTC) Received: from omta09.emeryville.ca.mail.comcast.net ([76.96.30.20]) by qmta03.emeryville.ca.mail.comcast.net with comcast id crPe1g0020S2fkCA3rPq5b; Thu, 28 Apr 2011 03:23:50 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta09.emeryville.ca.mail.comcast.net with comcast id crPo1g00W1t3BNj8VrPo1k; Thu, 28 Apr 2011 03:23:50 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 018D29B418; Wed, 27 Apr 2011 20:23:47 -0700 (PDT) Date: Wed, 27 Apr 2011 20:23:47 -0700 From: Jeremy Chadwick To: Rumen Telbizov Message-ID: <20110428032347.GA15220@icarus.home.lan> References: <20110427125736.GA1977@icarus.home.lan> <4DB8381B.4030408@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Denny Schierz , Alexander Motin , FreeBSD Stable Subject: Re: MPS driver: force bus rescan after remove SAS cable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2011 03:23:51 -0000 On Wed, Apr 27, 2011 at 08:07:34PM -0700, Rumen Telbizov wrote: > I confirm I experience the same behavior with just a SAS expander not > via SAS switch. I've got no way to get my block device back but > reboot. I don't mean to sound critical, but why do you guys do this? The reason I ask: on actual production filers (read: NetApps), you don't go yanking out the FC cable between the HBA and the NA and expect everything to "be happy" afterwards. Most SAN administrators tend to reboot an appliance when doing this kind of work -- because this kind of work is considered maintenance. I understand what you folks are reporting is a problem. I'm just wondering why you're complaining about having to reboot a machine with an HBA in it after doing this kind of *physical* cabling work. My immediate thought is "I'm really not surprised". I guess some other people *are* surprised. :-) > Also identify function doesn't work from the OS (no problem > via the card BIOS). Don't remember having any luck with sg3_util > package either but worth trying again. I don't use SAS myself, but wouldn't the command be "inquiry" and not "identify"? "identify" is for ATA (specifically SATA via CAM), while "inquiry" is for SCSI. Where SAS fits into this is unknown to me. > On a related note: recently LSI released version 9.0 of their firmware > for SAS2008 and I found it fixes certain performance problems with > SuperMicro backplanes! In another thread, or a PR, if you could provide those technical details that would be beneficial. There are a very large number of FreeBSD users who use Supermicro server-class hardware, and I'm certain they would be interested in a full disclosure. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |