2 ms·
Refering to this?: http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULLS_in_some_files_after_recovery_when_I_unplugged_the_power.3F http://xfs.org/index
by e12e 11y ago
Refering to this?: http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULLS_in_some_files_after_recovery_when_I_unplugged_the_power.3F http://xfs.org/index.php/XFS_FAQ#Q:_Why_do_I_see_binary_NULL...
Are you sure it was worse than ext2/3?
[ed: Looks like it might be better/as good as ext2, but somewhat worse than ext3/4 -- apparently xfs jourunals only metadata: http://superuser.com/questions/84257/xfs-and-loss-of-data-when-power-goes-down http://superuser.com/questions/84257/xfs-and-loss-of-data-wh...
Still doesn't seem like it destroy's data on powerloss -- just the usual - if data isn't written to disk, then it's not written to disk.]
- aidenn0 11y agoYeah, still better than ext2. I think part of it is that many people expect the file to either not have grown, or have the data you wrote to it. IIRC (and I'm a bit hazy) here were other issues too that have been since fixed. The long delay between write and commit meant that a lot of bugs that would otherwise have been vanishingly rare got exposed. Likely the ext systems have/had similar bugs that just have only happened a single digit number of times in the past 20 years.
- the_why_of_y 11y agoext3 with the default data=ordered was the filesystem that taught a generation of Linux developers that fsync(2) does nothing to improve data consistency and has crippling performance impact, so should never ever be called. The inevitable results of applications developed for ext3 running on other file systems incurring data loss on system crashes then got blamed on those other filesystems (including ext4, ironically).