From: "Theodore Ts'o" <tytso@mit.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Margit Schubert-While <margitsw@t-online.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.20-rc3 ext3 fsck corruption -- tool update warning needed?
Date: Wed, 27 Nov 2002 15:47:19 -0500 [thread overview]
Message-ID: <20021127204718.GA10163@think.thunk.org> (raw)
In-Reply-To: <1038410337.6394.44.camel@irongate.swansea.linux.org.uk>
On Wed, Nov 27, 2002 at 03:18:57PM +0000, Alan Cox wrote:
> On Wed, 2002-11-27 at 13:39, Margit Schubert-While wrote:
> > >Fortunately, 1.28 didn't get adopted by any distro's as far as I know,
> > It got into Suse 8.1
>
> I guess thats a bit of showstopper for this change 8(
I forgot about SuSE; yeah, they are using 1.28, but they did take the
patch. (It's needed regardless of whether or not you're using HTREE
in the kernel; it can cause corrupted directories even if you're not
using ext3 htree's).
That being said, from what I can tell, SuSE does *not* support the
Htree changes, and you would be strongly advised to update to update
to the latest version of e2fsprogs before you enabled HTREE. The
version of e2fsck that SuSE is missing some checks that detect some
incosistencies in the htree structure (not a bug deal, but it might
miss some corrupted filesystems) and is also missing some endian
bugfixes in the htree code (only a problem if you're using a
big-endian machine).
- Ted
next prev parent reply other threads:[~2002-11-27 20:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 13:39 2.4.20-rc3 ext3 fsck corruption -- tool update warning needed? Margit Schubert-While
2002-11-27 15:18 ` Alan Cox
2002-11-27 20:47 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-25 5:12 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
2002-11-28 23:47 ` GertJan Spoelman
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=20021127204718.GA10163@think.thunk.org \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=margitsw@t-online.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