On Thu, 7 Aug 2003, Tom Oehser wrote:
>
> > AFAIK even 1.7.361 is able to mount any ext2/3 filesystem, however, it
>
> I think ext2 can only mount *clean* ext3 filesystems, if there is
> journalling to apply, doesn't it set a bit that stops it? There
> may be a 'force' flag or something, but it is definitely best to
> use ext3 if it isn't clean. The 1.7.361 should be able to mount
> it if it is clean.
Oh yes, "couldn't mount because of unsupported optional features";
and you need tune2fs to remove that flag.
Or debugfs:
$ debugfs -w /dev/hda1
debugfs: feature ^has_journal
debugfs: feature ^needs_recovery
debugfs: q
$ e2fsck -y -f /dev/hda1
$
You don't actually have to e2fsck, you can just mount it read only anyway.
Actually, it might be better not to run e2fsck, less chance of the dodgy
disk really ****ing things up.
BTW: The filesystem is NOT ext3 after this, it's a slightly corrupted
ext2 (even after running e2fsck from tomsrtbt).
--
Rob. (Robert de Bath <robert$ @ debath.co.uk>)
<http://www.cix.co.uk/~mayday>
Google Homepage: http://www.google.com/search?btnI&q=Robert+de+Bath
