I agree with Daniel's comment #113. The data integrity semantics of ext3's data=ordered is indeed useful in practice, and ext4 should not introduce different semantics (essentially no safer than data=writeback) for the option with the same name. The current behavior should be called "data=ordered_for_allocated", and described as a mode where files updated via create/rename without fsync() can be totally lost in case of a power failure, but no random and possibly sensitive data from other users may possibly end up in it.
Thank you, Theodore, for explaining that turning off delayed allocation solves the problem. Is it possible to delay allocation until transaction commit time? -- Ext4 data loss https://bugs.launchpad.net/bugs/317781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
