public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Andries.Brouwer@cwi.nl
Cc: daniel@rimspace.net, linux-kernel@vger.kernel.org
Subject: Re: 2.5.12 severe ext3 filesystem corruption warning!
Date: Thu, 02 May 2002 14:58:13 -0700	[thread overview]
Message-ID: <3CD1B675.BBFBA61B@zip.com.au> (raw)
In-Reply-To: <UTC200205022140.g42Le8N14139.aeb@smtp.cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> 
> >> 2.5.12, serious ext3 filesystem corrupting behavior
> 
> I have had problems with 2.5.10 (first few blocks of the root
> filesystem overwritten) and then went back to 2.5.8 that I had
> used for a while already, but then also noticed corruption there.
> Back at 2.4.17 today..
> 
> In my case the problem was almost certainly the IDE code.

hmm.  Maybe.  As Al says, the fact that it concerned
mapped files is deeply fishy.

Daniel, could you please check your logs for IDE
errors and "buffer layer errors" and also tell us
(as much as you can remember) the names of all the
affected files, and what application would have
written them.

Thanks.

-

  parent reply	other threads:[~2002-05-02 21:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 21:40 2.5.12 severe ext3 filesystem corruption warning! Andries.Brouwer
2002-05-02 20:50 ` Martin Dalecki
2002-05-02 21:58 ` Andrew Morton [this message]
2002-05-02 22:57   ` Daniel Pittman
2002-05-04  5:26     ` Milton Miller
2002-05-04  5:46       ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2002-05-02 13:01 Daniel Pittman
2002-05-02 19:21 ` Andrew Morton
2002-05-02 19:34   ` Alexander Viro
2002-05-02 20:34     ` Andrew Morton
2002-05-02 22:39       ` Daniel Pittman
2002-05-02 22:37   ` Daniel Pittman
2002-05-02 23:00     ` Andrew Morton
2002-05-03  0:02       ` Daniel Pittman

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=3CD1B675.BBFBA61B@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=daniel@rimspace.net \
    --cc=linux-kernel@vger.kernel.org \
    /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