From owner-freebsd-stable@FreeBSD.ORG Mon Jan 15 02:28:03 2007 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 5663116A412 for ; Mon, 15 Jan 2007 02:28:03 +0000 (UTC) (envelope-from geoffwa@cs.rmit.edu.au) Received: from its-mu-mail1.its.rmit.edu.au (its-mu-mail1.its.rmit.edu.au [131.170.1.11]) by mx1.freebsd.org (Postfix) with ESMTP id F148C13C45A for ; Mon, 15 Jan 2007 02:28:02 +0000 (UTC) (envelope-from geoffwa@cs.rmit.edu.au) Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by its-mu-mail1.its.rmit.edu.au (8.13.7/8.13.7/mail1) with ESMTP id l0F23HiP002543 for ; Mon, 15 Jan 2007 13:04:28 +1100 (EST) Received: from goanna.cs.rmit.edu.au (root@goanna.cs.rmit.edu.au [131.170.24.40]) by wombat.cs.rmit.edu.au (8.12.10/8.12.10/cshub) with ESMTP id l0F1gDU6025284 for ; Mon, 15 Jan 2007 12:42:13 +1100 (EST) Received: from goanna.cs.rmit.edu.au (geoffwa@localhost [127.0.0.1]) by goanna.cs.rmit.edu.au (8.13.4+Sun/8.13.4/csnode) with ESMTP id l0F1gDbV000553 for ; Mon, 15 Jan 2007 12:42:13 +1100 (EST) Received: (from geoffwa@localhost) by goanna.cs.rmit.edu.au (8.13.4+Sun/8.13.3/Submit) id l0F1gDUf000552 for freebsd-stable@freebsd.org; Mon, 15 Jan 2007 12:42:13 +1100 (EST) Date: Mon, 15 Jan 2007 12:42:13 +1100 From: Geoffrey Giesemann To: freebsd-stable@freebsd.org Message-ID: <20070115014213.GA29074@cs.rmit.edu.au> References: <20070105165910.GA37906@zone3000.net> <20070107164336.GA13511@crodrigues.org> <200701071922.l07JMp3K016382@lava.sentex.ca> <20070107213350.GA61293@aleph.niw.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070107213350.GA61293@aleph.niw.com.au> User-Agent: Mutt/1.5.11 X-Scanned-By: MIMEDefang 2.44 Subject: Re: kernel panic on 6.2-RC2 with GENERIC. 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: Mon, 15 Jan 2007 02:28:03 -0000 On Mon, Jan 08, 2007 at 08:03:50AM +1030, Ian West wrote: > On Sun, Jan 07, 2007 at 02:25:02PM -0500, Mike Tancsa wrote: > > At 11:43 AM 1/7/2007, Craig Rodrigues wrote: > > >On Fri, Jan 05, 2007 at 06:59:10PM +0200, Nikolay Pavlov wrote: > > > > > I have seen this identical fault with the new areca driver, my machine > is opteron hardware, but running a regular i386/SMP kernel/world. With > everything at 6.2RC2 (as of 29th of December) except the areca driver > the machine is rock solid, with the 29th of december version of the > areca driver the box will crash on extract of a large tar file, removal > of a large directory structure, or pretty much anything that does a lot > of disk io to different files/locations. There is no error log prior to > seeing the following messages.. > > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433078272, length=8192)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433111040, length=16384)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433209344, length=16384)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=433242112, length=32768)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437612544, length=4096)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437616640, length=12288)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437633024, length=6144)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437639168, length=2048)]error = 5 > Dec 29 14:26:44 aleph kernel: g_vfs_done():da0s1g[WRITE(offset=437641216, length=6144)]error = 5 > > There are a string of these, followed by a crash and reboot. The file system > state can be left very dirty to the point where background fsck seems unable > to recover it. > > The areca card in question is running the latest firmware/boot and > has shown no problems either before, or since backing out the areca > driver. > > The volume is ran the tests on was a 250G on a raid6 raid set. > I've had exactly the same issue on my arcmsr in a i386/SMP box. The card is in a 64bit/66Mhz slot running the lastest firmware and the kernel is recent. I triggered it by creating a large number of files (~10^3 to 10^4) using Samba. This caused similar errors on two volumes on a ~800GB RAID5 array. Turning off soft-updates cured the crash, but not the write errors. --Geoff