Date: Mon, 15 Jan 2007 12:42:13 +1100 From: Geoffrey Giesemann <geoffwa@cs.rmit.edu.au> To: freebsd-stable@freebsd.org Subject: Re: kernel panic on 6.2-RC2 with GENERIC. Message-ID: <20070115014213.GA29074@cs.rmit.edu.au> In-Reply-To: <20070107213350.GA61293@aleph.niw.com.au> References: <20070105165910.GA37906@zone3000.net> <20070107164336.GA13511@crodrigues.org> <200701071922.l07JMp3K016382@lava.sentex.ca> <20070107213350.GA61293@aleph.niw.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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: > > > <snip> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070115014213.GA29074>