From owner-freebsd-fs@FreeBSD.ORG Mon Nov 7 09:22:53 2011 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 482F91065670; Mon, 7 Nov 2011 09:22:53 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id CBB6E8FC24; Mon, 7 Nov 2011 09:22:52 +0000 (UTC) Received: by qadb12 with SMTP id b12so2346282qad.13 for ; Mon, 07 Nov 2011 01:22:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=7tlGToQ+TyuJS4hlFip2dDFGqpO3lkVwaCsHg3eIWPY=; b=fJfw5AGM1634meM2INBzq+9WoGzfirbQh3IvnTkSqVMLf4GDTNNkXLumQmOGCORmub u5GXDlHFAOV38JpWPpBA7sPCbqx2pnFd8Fac0V29xJFqinv46TILw8S7zZa5usipB+hS 5b6UrxPoMtYAPT5aV4mDEsw/oEvOGAQ5EKhbE= MIME-Version: 1.0 Received: by 10.229.65.27 with SMTP id g27mr2359222qci.288.1320656174318; Mon, 07 Nov 2011 00:56:14 -0800 (PST) Sender: rincebrain@gmail.com Received: by 10.229.138.14 with HTTP; Mon, 7 Nov 2011 00:56:14 -0800 (PST) In-Reply-To: <75BDE9FA-6130-4BB4-8518-275D68BB3E49@slu.se> References: <82B38DBF-DD3A-46CD-93F6-02CDB6506E05@slu.se> <20111025193302.GA30409@nargothrond.kdm.org> <20111026101602.GA9768@icarus.home.lan> <75BDE9FA-6130-4BB4-8518-275D68BB3E49@slu.se> Date: Mon, 7 Nov 2011 03:56:14 -0500 X-Google-Sender-Auth: zmMH5-mOzoXy4iUoPfLnn9EKedo Message-ID: From: Rich To: =?ISO-8859-1?Q?Karli_Sj=F6berg?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-scsi@freebsd.org" , "Kenneth D. Merry" , "fs@freebsd.org" Subject: Re: AOC-USAS2-L8i zfs panics and SCSI errors in messages 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: Mon, 07 Nov 2011 09:22:53 -0000 Observation - the LSI SAS expanders, in my experience, sometimes misbehave when there are drives which respond slower than some timeout to commands (as far as I've seen it's only SATA drives it does this for, but I don't have many SAS drives for comparison), leading to all further commands to that drive for a bit not working, and then what happens depending on the OS varies dramatically. If you could try without an expander (e.g. with 1->4 SAS->SATA fanout cables), you may be surprised (and/or annoyed) to find your life gets better. - Rich On Mon, Nov 7, 2011 at 3:48 AM, Karli Sj=F6berg wrot= e: > As a test, I have copied in about 1.5TB and scrubbed several times withou= t any panic. It stayed solid until periodic weekly:( Same panic as with dai= ly. > > /Karli Sj=F6berg > > 26 okt 2011 kl. 12.16 skrev Jeremy Chadwick: > > On Wed, Oct 26, 2011 at 11:36:44AM +0200, Karli Sj?berg wrote: > Hi all, > > I tracked down what causes the panics! > > I got a tip from aragon and phoenix at the forum about > /etc/periodic/security/100.chksetuid > > And to put: > daily_status_security_chksetuid_enable=3D"NO" > into /etc/periodic.conf > > This is not truly the cause of the panic, it simply exacerbates it. > > Many of the periodic scripts will do things like iterate over all files > on the filesystem looking for specific attributes, etc.. =A0This tends to > stress filesystems heavily. =A0This isn't the only one. =A0:-) > > I can now run periodic daily without any panics. I?m still wondering > about the cause of this, the explanation from the forum was that that > phase is too demanding for multi TB systems. But I have several multi > TB servers with FreeBSD and ZFS, and none of them has ever behaved > this way. Besides, the panic is instantaneous, not degenerative. I > imagine that a run like that would start out OK and then just get > worse and worse, getting gradually slower and slower until it just > wouldn?t cope any more and hang. This feels more like hitting a wall. > As if it found something that is couldn?t deal with and has no choice > but to panic immediately. > > It may be possible that you have some underlying filesystem corruption > that triggers this situation. =A0Have you actually tried doing a "zpool > scrub" of your pools and seeing if any errors happen or if the panic > occurs there? > > I'm inclined to think what you're experiencing is probably a bug or > "quirk" in the storage controller driver you're using. =A0There are other > drivers that have had fixes applied to them "to make them work decently > with ZFS", meaning the kind of stressful I/O ZFS puts on them results in > the controller driver behaving oddly or freaking out, case in point. =A0I= t > could also be a controller firmware bug/quirk/design issue. =A0Seriously. > > I believe the AOC-USAS2-L8i controller has been discussed on > freebsd-stable, re: mps(4) driver problems or equivalent, but I'm not > going to CC that list given that there would be 3 cross-posted lists > involved and that is liable to upset some folks. =A0You should search the > mailing lists for discussion of Supermicro controllers that work > reliably with FreeBSD. > > It would be worthwhile to discuss this condition on -stable, mainly with > something like "Anyone else using the AOC-USAS2-L8i reliably with ZFS?" > You get the idea. > > -- > | Jeremy Chadwick =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0jdc at parodius.com | > | Parodius Networking =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://= www.parodius.com/ | > | UNIX Systems Administrator =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Mountain= View, CA, US | > | Making life hard for others since 1977. =A0 =A0 =A0 =A0 =A0 =A0 =A0 PGP= 4BD6C0CB | > > > > > Med V=E4nliga H=E4lsningar > -------------------------------------------------------------------------= ------ > Karli Sj=F6berg > Swedish University of Agricultural Sciences > Box 7079 (Visiting Address Kron=E5sv=E4gen 8) > S-750 07 Uppsala, Sweden > Phone: =A0+46-(0)18-67 15 66 > karli.sjoberg@slu.se > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >