From: Tony Gale <gale@syntax.dera.gov.uk>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Andreas Dilger <adilger@turbolinux.com>,
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: 26 Jun 2001 10:27:14 +0100 [thread overview]
Message-ID: <993547634.11781.0.camel@syntax.dera.gov.uk> (raw)
In-Reply-To: <01062600253207.01008@starship>
In-Reply-To: <200106251951.f5PJpOYN025503@webber.adilger.int> <01062600253207.01008@starship>
I use debugfs to remove the flag before fsck'ing:
Start debugfs.
Type
open -f -w /dev/<part>
features -FEATURE_C5
-tony
On 26 Jun 2001 00:25:32 +0200, Daniel Phillips wrote:
> On Monday 25 June 2001 21:51, Andreas Dilger wrote:
> > Daniel writes:
> > > Sure, if your root partition is expendable, by all means go ahead. Ted
> > > has already offered to start the required changes to e2fsck, which
> > > reminds me, I have to send the promised docs. For now, just use normal
> > > fsck and it will (in theory) turn the directory indexes back into normal
> > > file blocks, and have no effect on inodes.
> >
> > 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.
>
> BTW, there doesn't seem to be a --version command in tune2fs.
>
next prev parent reply other threads:[~2001-06-26 9:27 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 [this message]
2001-06-26 23:49 ` Theodore Tso
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=993547634.11781.0.camel@syntax.dera.gov.uk \
--to=gale@syntax.dera.gov.uk \
--cc=adilger@turbolinux.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=f.v.heusden@ftr.nl \
--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