Date: Sun, 9 May 2004 17:21:28 +0200 From: Adriaan de Groot <adridg@cs.kun.nl> To: freebsd-amd64@freebsd.org Subject: Re: NFS or ATA driver causes FS corruption? Message-ID: <200405091721.33399.adridg@cs.kun.nl> In-Reply-To: <Pine.BSF.4.53.0405081806240.66978@e0-0.zab2.int.zabbadoz.net> References: <20040302031226.GA670@xor.obsecurity.org> <4044297F.1080701@DeepCore.dk> <Pine.BSF.4.53.0405081806240.66978@e0-0.zab2.int.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 08 May 2004 20:25, Bjoern A. Zeeb wrote:
> On Mon, 1 Mar 2004, it was written:
> > Kris Kennaway wrote:
> > > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=3D9=
440
> > > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=3D2=
0904
> >
> > The above means that *something* is stomping on the taskqueue that
> > should take care of returning finished requests to the system (they are
I see this (timeouts fired) as well on my Asus K8V with a single S-ATA disk=
;=20
it happens only when the machine is ridiculously loaded (like feeding a=20
5500-message mbox file into sa-learn while doing two different make -j6=20
compiles and also cvsupping the FBSD tree along with another 2G source repo=
).=20
Haven't noticed any averse effects, though - the machine chokes for 30=20
seconds or so and then carries on.
=2D --=20
"On top of that [watching KDE CVS] is interesting in a perverse=20
way, like watching sausage get made. By very smart people." - dkite
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAnkx9dqzuAf6io/4RAt6yAJwOQpEBIjpL6b77wv6otIR2dcoW3QCfd+ze
pf7E2zqAvBF6UHxJuzgdvL0=3D
=3DyAzd
=2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405091721.33399.adridg>