Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 30 Sep 2015 13:39:15 +1300
From:      Philip Murray <pmurray@nevada.net.nz>
To:        Graham Allan <allan@physics.umn.edu>
Cc:        =?utf-8?Q?Karli_Sj=C3=B6berg?= <karli.sjoberg@slu.se>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   Re: Cannot replace broken hard drive with LSI HBA
Message-ID:  <1A19B1E0-FC2F-4847-A3BA-E6F694589E4E@nevada.net.nz>
In-Reply-To: <560AF6AD.3010803@physics.umn.edu>
References:  <1443447383.5271.66.camel@data-b104.adm.slu.se> <5609578E.1050606@physics.umn.edu> <1443507440.5271.72.camel@data-b104.adm.slu.se> <560AF6AD.3010803@physics.umn.edu>

next in thread | previous in thread | raw e-mail | index | archive | help


> On 30/09/2015, at 9:38 am, Graham Allan <allan@physics.umn.edu> wrote:
>=20
> On 9/29/2015 1:17 AM, Karli Sj=C3=B6berg wrote:
>>>=20
>>> Regarding your experience with firmware 20, I believe it is "known =
bad",
>>> though some seem to disagree. Certainly when building my recent-ish
>>> large 9.3 servers I specifically tested it and got consistent data
>>> corruption. There is now a newer release of firmware 20 , =
"20.00.04.00"
>>> which seems to be fixed - see this thread:
>>>=20
>>> =
https://lists.freebsd.org/pipermail/freebsd-scsi/2015-August/006793.html
>>=20
>> No, firmware 20.00.04.00 and driver 20.00.00.00-fbsd was the one that
>> was used when ZFS freaked out, so it=C2=B4s definitely not fixed.
>>=20
>> I think this calls for a bug report.
>=20
> That is curious, since I could rapidly get data corruption with =
firmware 20.00.00.00, yet ran a stress test for about a week with =
20.00.04.00 with no issues. That was with FreeBSD 9.3, but I just =
updated my test system to 10.2, and it has been running the same stress =
test for 4-5 hours again with no issues. I don't doubt your experience =
at all, of course, but I wonder what is different?
>=20
> For what it's worth, my test machine is a Dell R610 with Dell TYVGC =
HBA (unclear whether this is a 9207-8e or 9205-8e), and WD Red drives in =
a Supermicro SC847 chassis.

Just as an additional datapoint (this thread is giving me chills) with =
the LSI IT firmware version 20.00.02.00=E2=80=A6

* FreeBSD 10.2-RELEASE
* Supermicro SC826 Chassis
* LSI SAS2004 Controller
	mps0: <Avago Technologies (LSI) SAS2004> port 0xe000-0xe0ff mem =
0xf72c0000-0xf72c3fff,0xf7280000-0xf72bffff irq 16 at device 0.0 on pci1
	mps0: Firmware: 20.00.02.00, Driver: 20.00.00.00-fbsd
	mps0: IOCCapabilities: =
1285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>=


* LSI SAS2X28 Expander/Backplane
	ses0: <LSI SAS2X28 0e12> Fixed Enclosure Services SPC-3 SCSI =
device=20

* 12x SATA WD RE 2TB  drives (WD2000FYYZ arranged as 2x RAIDZ2 vdevs)

Repeatedly filled up with data with regular scrubs without any issues =
and performance is pretty good, although I haven=E2=80=99t had a disk =
fail yet.=20

Cheers

Phil=20=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1A19B1E0-FC2F-4847-A3BA-E6F694589E4E>