public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: walt <walt@nea-fast.com>
Cc: linux-kernel@vger.kernel.org, akpm@zip.com.au,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: 2.4.19 ext3 oops with file system damage - possible nfs and ext3 not playing nice together
Date: Fri, 30 Aug 2002 00:59:31 +0100	[thread overview]
Message-ID: <20020830005931.D23868@redhat.com> (raw)
In-Reply-To: <200208281451.12117.walt@nea-fast.com>; from walt@nea-fast.com on Wed, Aug 28, 2002 at 02:51:12PM -0400

Hi,

On Wed, Aug 28, 2002 at 02:51:12PM -0400, walt wrote:
 
> without any errors being reported. When I'd try gunzip the file from CD, I'd 
> get CRC errors. I then tried mounting the ISO image and running gunzip and 
> I'd get the same CRC errors. 

That's usually a hardware or driver, not filesystem, problem.  I've
had a couple of environments which have given data corruptions like
that on IDE drivers in UDMA mode but which were fine in MDMA or PIO
mode.  

> no problems. All this was repeatable. I upgraded kernels from RedHat 7.3 
> stock  2.4.18-3 to vanilla 2.4.19 and problem seemed to go away. 

That can be just a matter of the config options used masking a driver
problem.  Can you still reproduce with "ide=nodma"?  That would
certainly point towards a driver or hardware fault.

--Stephen

      parent reply	other threads:[~2002-08-29 23:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 18:51 2.4.19 ext3 oops with file system damage - possible nfs and ext3 not playing nice together walt
2002-08-28 20:18 ` Andreas Dilger
2002-08-29 23:59 ` Stephen C. Tweedie [this message]

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=20020830005931.D23868@redhat.com \
    --to=sct@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=walt@nea-fast.com \
    /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