From owner-freebsd-fs@FreeBSD.ORG Fri Jan 20 09:09:17 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69A69106564A for ; Fri, 20 Jan 2012 09:09:17 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 501018FC0A for ; Fri, 20 Jan 2012 09:09:17 +0000 (UTC) Received: from omta11.emeryville.ca.mail.comcast.net ([76.96.30.36]) by qmta06.emeryville.ca.mail.comcast.net with comcast id Pl9G1i0030mlR8UA6l9Ga6; Fri, 20 Jan 2012 09:09:16 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta11.emeryville.ca.mail.comcast.net with comcast id Pl9G1i0031t3BNj8Xl9GMg; Fri, 20 Jan 2012 09:09:16 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id DF7E4102C19; Fri, 20 Jan 2012 01:09:15 -0800 (PST) Date: Fri, 20 Jan 2012 01:09:15 -0800 From: Jeremy Chadwick To: Peter Maloney Message-ID: <20120120090915.GA90876@icarus.home.lan> References: <4F192ADA.5020903@brockmann-consult.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4F192ADA.5020903@brockmann-consult.de> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: sanity check: is 9211-8i, on 8.3, with IT firmware still "the one" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2012 09:09:17 -0000 On Fri, Jan 20, 2012 at 09:50:34AM +0100, Peter Maloney wrote: > John, > > Various people have problems with mps and ZFS. > > I am using 8-STABLE from October 2011, and on the 9211-8i HBA, I am > using 9 IT firmware. In my case, it was the firmware on an SSD that > caused problems. > Crucial M4-CT256M4SSD2 firmware 0001 My below comment is unrelated to mps driver bugs and so on, but: Owners of Crucial m4 SSDs need to be aware of this catastrophic problem with the drives: Crucial m4 SSDs begin to fail (data loss) starting at the 5200 power-on-hours count. Apparently the problem is triggered by some sort of SMART-related ordeal as well (I have no details). This is a firmware bug and has been confirmed by Crucial. A firmware fix just came out a few days ago for the problem. Here's the URL where I was made aware of this problem (note the trailing hyphen please): http://www.dslreports.com/forum/r26745697- And media confirmations: http://www.theverge.com/2012/1/17/2713178/crucial-m4-ssd-firmware-update-fixes-recurring-bsod http://www.anandtech.com/show/5308/crucial-to-fix-m4-bsod-issue-in-two-weeks http://www.anandtech.com/show/5424/crucial-provides-a-firmware-update-for-m4-to-fix-the-bsod-issue I've now added Crucial to my SSD brands to avoid (currently OCZ and Crucial). Welcome to year 20xx, where nobody actually does quality assurance properly. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |