On Fri, Jul 27, 2001 at 02:39:37PM +0100, Alan Cox wrote:
> > I've been doing that most of the time. But I sometimes forget that.
> > But as I said, it's not something I expected from a journalled filesystem.
> You misunderstand journalling then
> A journalling file system can offer different levels of guarantee. With
> metadata only journalling you don't take any real performance hit but your
> file system is always consistent on reboot (consistent as in fsck would pass
> it) but it makes no guarantee that data blocks got written.
The default behaviour of ext3 does make this guarantee, for what it's
worth. If you want the more relaxed mode which doesn't enforce the
flushing of data blocks before a commit, you need to mount with "-o
> Full data journalling will give you what you expect but at a performance hit
> for many applications.
You can achieve the necessary ordering to avoid stale data blocks
after a crash without the penalty of writing all the data to the
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Aug 15 2001 - 21:00:19 EST