After today's call, I was poking around a bit to try and understand better how the async commit code plays with the write barrier.
journal_submit_commit_record seems to disable the barriers when async IO is enabled if I read the code correctly. If this is true, how can we provide any promises of on disk data integrity after an fsync()?
Regards, Ric -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
