Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 May 2004 16:25:23 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Adriaan de Groot <adridg@cs.kun.nl>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: NFS or ATA driver causes FS corruption?
Message-ID:  <Pine.BSF.4.53.0405091617410.66978@e0-0.zab2.int.zabbadoz.net>
In-Reply-To: <200405091721.33399.adridg@cs.kun.nl>
References:  <20040302031226.GA670@xor.obsecurity.org> <4044297F.1080701@DeepCore.dk> <Pine.BSF.4.53.0405081806240.66978@e0-0.zab2.int.zabbadoz.net> <200405091721.33399.adridg@cs.kun.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 May 2004, Adriaan de Groot wrote:

> 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=9440
> > > > ad0: WARNING - WRITE_DMA interrupt was seen but timeout fired LBA=20904
> > >
> > > 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;
> it happens only when the machine is ridiculously loaded (like feeding a
> 5500-message mbox file into sa-learn while doing two different make -j6
> compiles and also cvsupping the FBSD tree along with another 2G source repo).
> Haven't noticed any averse effects, though - the machine chokes for 30
> seconds or so and then carries on.

I have to hard reset the machine here :(

I can reproduce it with not too much IO. copying sources; make
buildworld, ...

I tried to do everything mentioned in the errata for 5.2(.1) but
nothing helped. It also happened with DMA disbaled (an d I thing it
logged PIO errors at that time).

I am now going to build a world from NFS src to NFS obj to not
have ATA traffic and to slow down things so this will not happen
(hopefully).
[ obj dir could be oon the same machine I suspect but the installworld
will then most likely make the machine go berserk again ].

Are you running Release or HEAD ?

If this isn't fix in HEAD yet I am very interested in every
patches/things to try to fix this. The machine in question should
become my new in house server and I do not like another IO problem
once I night when backup is running...

-- 
Greetings

Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
56 69 73 69 74				http://www.zabbadoz.net/



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0405091617410.66978>