From owner-freebsd-stable@FreeBSD.ORG Wed Dec 13 07:33:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7D2A16A4C9 for ; Wed, 13 Dec 2006 07:33:42 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88B9943CBC for ; Wed, 13 Dec 2006 07:32:09 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 1FA5F28432; Wed, 13 Dec 2006 01:33:36 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 75B6261C36; Wed, 13 Dec 2006 01:33:35 -0600 (CST) Date: Wed, 13 Dec 2006 01:33:35 -0600 From: "Matthew D. Fuller" To: Scott Long Message-ID: <20061213073335.GW31944@over-yonder.net> References: <00a601c71e7f$ed63f7a0$3301a8c0@janmxp> <457FAAFD.1080707@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <457FAAFD.1080707@samsco.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: Jan Mikkelsen , freebsd-stable@freebsd.org Subject: Re: g_vfs_done() failures on 6.2-RC1 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: Wed, 13 Dec 2006 07:33:42 -0000 On Wed, Dec 13, 2006 at 12:25:49AM -0700 I heard the voice of Scott Long, and lo! it spake thus: > > You mention that you are using a driver from the Areca website. > Have you tried using the stock driver that comes with FreeBSD? I > don't know if it will be better or not, but I was planning on doing > a refresh of the stock driver, and I'd hate to introduce instability > that wasn't there before. I don't think it's related to that. I know a guy who saw similar errors on an ICH-6(?) controller (with no RAID) on some random RELENG_6, ending up in somewhat wonky filesystems. I was inclined to blame the controller, since it ends up with SATA slave devices. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.