[Bug 37435] XFS does not leave garbage in file

[Stewart Smith]

It should be strongly noted that XFS will NOT leave garbage in the file. The only thing you'll ever get that is'nt your data is NULLs.

see here http://www.ussg.iu.edu/hypermail/linux/kernel/0407.1/0630.html

(better to show NULL than bogus data).

On the whole fsync issue,
http://www.ussg.iu.edu/hypermail/linux/kernel/0407.1/1072.html

(Chris is one of the guys who does know what he's talking about).

The followup message is hpa agreeing.


I also feel like I'm going in circles here. I've provided the correct semantics that need to be followed and backed it up (as have others) yet still you claim that file system semantics that follow the standard are somehow buggy.

Also, considering that dpkg runs on other systems (some where "fixing" the kernel simply isn't an option) it's best to fix dpkg, no?

Note that you'd possibly have the same bug with ext2 as well, possibly reiser 3 and UFS without soft updates.

-- 
XFS leaves garbage in file if app does write-new-then-rename without f(data)sync
https://launchpad.net/bugs/37435