From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ken@irridia.com (Ken Brownfield)
Cc: m.knoblauch@TeraPort.de,
linux-kernel@vger.kernel.org (linux-kernel@vger.kernel.org)
Subject: Re: Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2)
Date: Wed, 20 Mar 2002 01:31:46 +0000 (GMT) [thread overview]
Message-ID: <E16nUx8-0000w4-00@the-village.bc.nu> (raw)
In-Reply-To: <20020319190211.B15811@asooo.flowerfire.com> from "Ken Brownfield" at Mar 19, 2002 07:02:11 PM
> We're seeing this with Tyan 2410s and Seagate drives. I think Tyan just
> can't get DMA right. Luckily we mainly lost docs or man pages before we
> disabled DMA, although losing the rpm database sucked. MDMA2 seems okay
> but we haven't tested it long enough to form a lasting impression.
> I'm actually patching the ServerWorks driver to honor the CONFIG flag,
> since even with hdparm there is a narrow risk to the fs during the boot
> process before DMA is disabled.
I can confirm problems with serverworks OSB4 and UDMA. With UDMA and
a seagate disk you see 4 bytes repeat from one transfer into the next
shuffling all the data up 4 bytes (which since it includes inode and
metadata is *messy*). Current 2.4 has detect code that sometimes traps this
and panics to avoid fs death.
With MWDMA all was fine.
This was observed across a large number of boxes in a rendering farm so its
not a one off flawed box, and across two board vendors. I reported it to
serverworks who were interested but couldnt reproduce it in their lab.
next prev parent reply other threads:[~2002-03-20 1:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 18:42 Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2) Martin Knoblauch
2002-03-20 1:02 ` Ken Brownfield
2002-03-20 1:31 ` Alan Cox [this message]
2002-03-20 1:29 ` Andre Hedrick
2002-03-20 1:41 ` Ken Brownfield
2002-03-20 2:01 ` Alan Cox
2002-03-20 1:53 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP Alan Cox
2002-03-20 2:36 ` Andre Hedrick
2002-03-20 10:32 ` Alan Cox
2002-03-20 10:04 ` Martin Knoblauch
2002-03-20 15:27 ` Re[2]: " Nerijus Baliunas
2002-03-20 15:49 ` Alan Cox
2002-03-20 1:33 ` Filesystem Corruption (ext2) on Tyan S2462, 2xAMD1900MP, 2.4.17SMP (RH7.2) Ken Brownfield
2002-03-20 1:56 ` Alan Cox
2002-03-20 16:10 ` Vojtech Pavlik
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=E16nUx8-0000w4-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ken@irridia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.knoblauch@TeraPort.de \
/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;
as well as URLs for NNTP newsgroup(s).