From: Theodore Tso <tytso@valinux.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Tony Gale <gale@syntax.dera.gov.uk>,
Heusden@mail.bonn-fries.net, Folkert van <f.v.heusden@ftr.nl>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
Alexander Viro <viro@math.psu.edu>
Subject: Re: [Ext2-devel] Re: [UPDATE] Directory index for ext2
Date: Tue, 26 Jun 2001 19:49:19 -0400 [thread overview]
Message-ID: <20010626194919.J537@think.thunk.org> (raw)
In-Reply-To: <200106251951.f5PJpOYN025503@webber.adilger.int> <01062600253207.01008@starship>
In-Reply-To: <01062600253207.01008@starship>; from phillips@bonn-fries.net on Tue, Jun 26, 2001 at 12:25:32AM +0200
On Tue, Jun 26, 2001 at 12:25:32AM +0200, Daniel Phillips wrote:
> > This is only true without the COMPAT_DIR_INDEX flag. Since e2fsck _needs_
> > to know about every filesystem feature, it will (correctly) refuse to touch
> > such a system for now. You could "tune2fs -O ^FEATURE_C4 /dev/hdX" to
> > turn of the COMPAT_DIR_INDEX flag and let e2fsck go to town. That will
> > break all of the directory indexes, I believe.
>
> This is what he wants, a workaround so he can fsck. However, the above
> command (on version 1.2-WIP) just gives me:
>
> Invalid filesystem option set: ^FEATURE_C4
>
> Maybe he should just edit the source so it doesn't set the superblock flag
> for now.
I haven't had a chance to analyze the directory index format to see if
an-dirindexing-ignorant e2fsck could do any damage to the index. It's
probably the case as long as the filesystem isn't corrupted, simply
modifying e2fsck to ignore the compatibility flag won't hurt. But
it's certainly not something I would recommend for any kind of
production operation.
- Ted
next prev parent reply other threads:[~2001-06-26 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 16:13 [UPDATE] Directory index for ext2 Daniel Phillips
2001-05-31 19:44 ` [Ext2-devel] " Andreas Dilger
2001-05-31 21:02 ` Daniel Phillips
2001-05-31 22:42 ` Andreas Dilger
2001-06-03 0:19 ` Daniel Phillips
2001-06-20 14:59 ` Tony Gale
2001-06-20 16:02 ` [Ext2-devel] " Theodore Tso
2001-06-20 17:27 ` Daniel Phillips
2001-06-20 16:58 ` Daniel Phillips
2001-06-25 9:46 ` Tony Gale
2001-06-25 16:10 ` Daniel Phillips
2001-06-25 19:51 ` [Ext2-devel] " Andreas Dilger
2001-06-25 22:25 ` Daniel Phillips
2001-06-26 9:27 ` Tony Gale
2001-06-26 23:49 ` Theodore Tso [this message]
2001-06-27 0:08 ` [RFC] Checks in ext2_new_block() Alexander Viro
2001-07-03 10:00 ` [Ext2-devel] Re: [UPDATE] Directory index for ext2 Tony Gale
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=20010626194919.J537@think.thunk.org \
--to=tytso@valinux.com \
--cc=Heusden@mail.bonn-fries.net \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=f.v.heusden@ftr.nl \
--cc=gale@syntax.dera.gov.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=viro@math.psu.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