From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PROBLEM] NFS trouble - file corruptions
Date: 29 Nov 2002 14:32:52 +0000 [thread overview]
Message-ID: <1038580372.13625.8.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0211291410240.29442-100000@grignard.amagerkollegiet.dk>
On Fri, 2002-11-29 at 13:17, Rasmus Bøg Hansen wrote:
> I just tried turning off DMA on the server disk (this is just a low-end
> IDE-system): No errors in files (compressing the file thrice).
>
> So it does not at all seem to be a NFS-issue!
>
> I have no idea what is wrong. If the disk, cable or IDE controller does
> bit-flipping when DMA is turned on, why is the problem only seen with
> NFS? I have never seem corrupted files or metadata with DMA turned
> (except once long ago, when I experimented with high-transfer-modes - I
> haven't done that since)...
More likely it changes the timings. There is at least one other
possibility though. With some via bridges using slightly too slow DDR
RAM at a 133MHz clock works reliably _until_ you get a mix of CPU and
DMA traffic. It'll even pass memtest86.
So if its a VIA box, turn DMA back on, stick the bios into its load
failsafe defaults mode and see if that has an affect.
Alan
next prev parent reply other threads:[~2002-11-29 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 22:12 Rasmus Bøg Hansen
2002-11-27 22:39 ` Trond Myklebust
2002-11-28 9:46 ` Rasmus Bøg Hansen
2002-11-28 11:49 ` Rasmus Bøg Hansen
2002-11-28 16:24 ` Trond Myklebust
2002-11-28 18:12 ` Rasmus Bøg Hansen
2002-11-28 18:36 ` Trond Myklebust
2002-11-28 18:51 ` Rasmus Bøg Hansen
2002-11-29 13:17 ` Rasmus Bøg Hansen
2002-11-29 14:32 ` Alan Cox [this message]
2002-11-29 14:34 ` Rasmus Bøg Hansen
2002-12-01 12:37 ` Rasmus Bøg Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1038580372.13625.8.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®