https://bugzilla.kernel.org/show_bug.cgi?id=70121 --- Comment #6 from sworddragon2@xxxxxxx --- > How does the file system know that the file has "successfully been > written"? Secondly, even if we did know, in order to guarantee the > transaction semantics, we *always* update the journal first. Only > after the journals is updated, do we write back to the final location > on disk. So what you are suggesting just simply wouldn't work. It seems it is just a too major change. Maybe it is something that could be considered in ext5. > it just > makes it more likely, but if you crash at the wrong moment, you can > still lose data I have never seen a damaged file with full data journaling enabled. Can you show me a race condition so that I can reproduce it? Hm, maybe it would be possible if the journal is smaller than the file (I'm wondering what would happen in such a case). -- You are receiving this mail because: You are watching the assignee of the bug. -- 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
