Messages in this thread | | | From | Daniel Phillips <> | Subject | Re: [Ext2-devel] Re: [UPDATE] Directory index for ext2 | Date | Tue, 26 Jun 2001 00:25:32 +0200 |
| |
On Monday 25 June 2001 21:51, Andreas Dilger wrote: > Daniel writes: > > > > On Wednesday 20 June 2001 16:59, Tony Gale wrote: > > > > > The main problem I have with this is that e2fsck doesn't know how > > > > > to deal with it - at least I haven't found a version that will. > > > > > This makes it rather difficult to use, especially for your root fs. > > > > 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.
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |