From: Andries Brouwer <aebr@win.tue.nl>
To: "Theodore Ts'o" <tytso@mit.edu>,
Clemmitt Sigler <siglercm@jrt.me.vt.edu>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
Alan Cox <Alan.Cox@linux.org>
Subject: Re: 2.4.20-rc3 ext3 fsck corruption -- tool update warning needed?
Date: Thu, 28 Nov 2002 23:49:30 +0100 [thread overview]
Message-ID: <20021128224930.GA5861@win.tue.nl> (raw)
In-Reply-To: <20021127125547.GA7903@think.thunk.org>
On Wed, Nov 27, 2002 at 07:55:48AM -0500, Theodore Ts'o wrote:
> Ah, ha. I think I know what happened.
>
> What version of e2fsprogs were you using? If it was 1.28, that would
> explain what you saw. There was a fencepost error that could corrupt
> directories when it was optimizing/rehashing them. This bug was fixed
> in in the next version, which was rushed out the door as a result of
> this bug. Fortunately, 1.28 didn't get adopted by any distro's as far
> as I know
Hmm. On a recently installed SuSE 8.1 machine:
% rpm -qf `which e2fsck`
e2fsprogs-1.28-18
(maybe the -18 contains the fix?)
next prev parent reply other threads:[~2002-11-28 22:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 5:12 2.4.20-rc3 ext3 fsck corruption -- tool update warning needed? Clemmitt Sigler
2002-11-25 10:57 ` Hugo Mills
2002-11-25 14:21 ` Clemmitt Sigler
2002-11-26 3:55 ` Theodore Ts'o
2002-11-25 17:15 ` Matthias Andree
2002-11-25 17:39 ` Tomas Konir
2002-11-25 18:37 ` Clemmitt Sigler
2002-11-26 2:47 ` Theodore Ts'o
2002-11-26 15:55 ` Clemmitt Sigler
2002-11-27 12:55 ` Theodore Ts'o
2002-11-27 14:28 ` Clemmitt Sigler
2002-11-28 22:49 ` Andries Brouwer [this message]
2002-11-28 23:47 ` GertJan Spoelman
-- strict thread matches above, loose matches on Subject: below --
2002-11-27 13:39 Margit Schubert-While
2002-11-27 15:18 ` Alan Cox
2002-11-27 20:47 ` Theodore Ts'o
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=20021128224930.GA5861@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=Alan.Cox@linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=siglercm@jrt.me.vt.edu \
--cc=tytso@mit.edu \
/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