> data=journal
>
> All data (as well as to metadata) is written to the journal
> before it is released to the main fs for writeback.
>
> This is a specialised mode - for normal fs usage you're better
> off using ordered data, which has the same benefits of not corrupting
> data after crash+recovery. However for applications which require
> synchronous operation such as mail spools and synchronously exported
> NFS servers, this can be a performance win. I have seen dbench
In ordered and journal mode, are meta data operations, namely creating a
file, rename(), link(), unlink() "synchronous" in the sense that after
the call has returned, the effect of this call is never lost, i. e., if
link(2) has returned and the machine crashes immediately, will the next
recovery ALWAYS recover the link?
Or will ext3 still need chattr +S?
Does it still support chattr +S at all?
Synchronous meta data operations are crucial for mail transfer agents
such as Postfix or qmail. Postfix has up until now been setting
chattr +S /var/spool/postfix, making original (esp. soft-updating) BSD
file systems significantly faster for data (payload) writes in this
directory than ext2.
Note: I'm not on the ext3-users list. Please Cc: back replies.
-- Matthias Andree - 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/