In data=ordered mode the ext3_ordered_commit_write function marks the buffers as dirty, how then does the JBD ensure that the data is written before the metadata? Once the data buffers are marked as dirty, JBD doesn't have control anymore over when the data is written is actually written to disk right? Because the actually writing of the data is handled by the page wtriteback mechanism (pdflush) right? I might be missing something here, thanks for your time and patience. -Joel -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html