file open -> disk full -> save -> file 0 byte

Bodo Thiesen bothie at
Wed Oct 20 02:01:43 UTC 2010

* Andreas Dilger <adilger.kernel at> hat geschrieben:

>> Bodo Thiesen schrieb:
>>> As to my knowledge, it is still impossible to mount an ext2 file system
>>> with the needs_recovery flag read only with the ext3 driver and because
>>> that flag is wrongly made "incompatible", it's  even impossible to mount
>>> it with the ext2 driver.
> Note that the needs_recovery flag was INTENTIONALLY made incompatible, not
> "wrongly" so.  That is because with metadata being written into the
> journal, there is no guarantee that the filesystem is even consistent when
> mounted without journal replay.  Metadata blocks can be reallocated as
> data blocks and overwritten by data, based only on changes committed to
> the journal, and this could result in errors.

Right ... except ... what is the difference between an ext2 filesystem
without journal which was not cleanly unmounted and one with journal which
was not cleanly unmounted (except for the fact, that the latter one can be
made consistent by replaying the journal in a few seconds). Especially:
Why would it make a difference when mounting it -o ro -t ext2?

Making errors intentionally is not really an excuse for doing so.

Regards, Bodo

More information about the Ext3-users mailing list