From owner-freebsd-scsi@FreeBSD.ORG Thu Jul 10 11:33:22 2014 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A73A5A54 for ; Thu, 10 Jul 2014 11:33:22 +0000 (UTC) Received: from gw.zefyris.com (sabik.zefyris.com [IPv6:2001:7a8:3c67:2::254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37BAB2072 for ; Thu, 10 Jul 2014 11:33:22 +0000 (UTC) Received: from sekishi.zefyris.com (sekishi.zefyris.com [IPv6:2001:7a8:3c67:2::12]) by gw.zefyris.com (8.14.5/8.14.5) with ESMTP id s6ABXJ20012141; Thu, 10 Jul 2014 13:33:19 +0200 (CEST) Date: Thu, 10 Jul 2014 13:33:19 +0200 From: Francois Tigeot To: Steven Hartland Subject: Re: Data corruption with the mfi(4) driver Message-ID: <20140710113315.GA3449@sekishi.zefyris.com> References: <20140710092251.GA1206@sekishi.zefyris.com> <20140710105307.GD1206@sekishi.zefyris.com> <765694DA8A58468484623092946127D1@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <765694DA8A58468484623092946127D1@multiplay.co.uk> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gw.zefyris.com [IPv6:2001:7a8:3c67:2::254]); Thu, 10 Jul 2014 13:33:20 +0200 (CEST) Cc: FreeBSD-scsi X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2014 11:33:22 -0000 On Thu, Jul 10, 2014 at 12:24:21PM +0100, Steven Hartland wrote: > > The key thing to determine here are precise factors of the corruption your > seeing as it looks like there is some mixing up of issues My original mail was intended as a head's up notice; I don't have enough information to fill in every detail and point to a particular root cause so far. > Given this could you confirm:- > 1. Hardware > 1.1. LSI card / generation Dell Rx20 server generation I have personally seen the issue on a Dell R720xd with a LSI Dell Perc H710 adapter. PCI Id: mfi0@pci0:3:0:0: class=0x010400 card=0x1f341028 chip=0x005b1000 rev=0x05 hdr=0x00 but have had private reports from at least two different machines having the same problem. All other parameters are variable. -- Francois Tigeot