Richard Smith wrote:
>
> Is there some way to fix this? This feels very fragile to me.
Just to be clear: this is _expected_ behaviour. Ext3 is
backward-compatible with ext2 _if_ it's mounted uncleanly and the
journal is clear. If there are writes outstanding in the journal then it
is not compatible with ext2. Thus the refusal to mount, with an error
message about incompatible features.
That may be the error I've seen. Not sure why a reset would fix it though.
How much of as space hit are we going to take if we use ext3 rather
than ext2 in the boot kernel?
if we just umount the ext3 cleanly, no need to do this.
I have not tried building it in, but we can try ...
ron
_______________________________________________
Devel mailing list
[email protected]
http://mailman.laptop.org/mailman/listinfo/devel
