Re: ext3 partition unmountable

Riley Williams (rhw@MemAlpha.CX)
Sat, 18 Aug 2001 23:04:41 +0100 (BST)


Hi Dewet.

>> If I'm reading the files right it looks like:
>> #define EXT3_FEATURE_INCOMPAT_COMPRESSION 0x0001

>> Did you compress the file system?

> Not knowingly, no. Is that a mount option?

The relevant mount option is to specify the ext3 rather than the ext2
file system, and the flag you refer to gets set if ANYBODY sets the
"COMPRESS THIS FILE" flag on ANY file on that file system. As far as I
can tell, nothing ever resets that flag, even if the last file that
was compressed gets uncompressed.

I suggested a while back that fsck should check whether there are any
compressed files on the filesystem, and reset that flag if not, but as
far as I can tell, nothing was ever done to implement that suggestion.

> I'm mounting them the same on both sides, so its rather
> strange...

>> Do a "tune2fs -l /dev/hdc" and see what features are set.

> Heh, not much more useful:

> # tune2fs -l /dev/hdd1
> tune2fs 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09
> tune2fs: Filesystem has unsupported feature(s) while trying to open /dev/hdd1
> Couldn't find valid filesystem superblock.

You have an old version of tune2fs, and need to get the one that knows
about ext3 or alternatively apply the patch that was distributed some
time ago and recompile - I'm not sure which.

Stephen: What's the current status regarding tune2fs and ext3, I'm a
tad out of date in this respect?

> I'll probably have to take the drive back, and see if it now mounts
> in the original system :-/

That might help...

Best wishes from Riley.

-
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/