Recent Features
| |||||||||||||
Ext4 filesystem hits Android, no need to fear data loss (ars technica)Ext4 filesystem hits Android, no need to fear data loss (ars technica)Posted Dec 28, 2010 12:37 UTC (Tue) by drag (subscriber, #31333)In reply to: Ext4 filesystem hits Android, no need to fear data loss (ars technica) by mjg59 Parent article: Ext4 filesystem hits Android, no need to fear data loss (ars technica)
On a side note, with BTRFS the write-then-rename without fsync is a safe operation.
Looks like this is guaranteed behavior on Linux now. :)
(Log in to post comments)
Well, is's quite explicit decision... Posted Dec 28, 2010 13:37 UTC (Tue) by khim (subscriber, #9252) [Link] This is true for more then year: see here. Filesystem developers don't like to support such semantic, but they all agree that "the application developers outnumber us" so it's simpler to explicitly add such guarantee rather then try to educate said application developers.
Well, is's quite explicit decision... Posted Dec 28, 2010 17:23 UTC (Tue) by Wol (guest, #4433) [Link]
It's not that fielsystem developers are outnumbered by app developers. It's that forcing app writers to do an fsync will simply KILL performance as pretty much every app will forever be hanging on file-system access.
Plus the fact that on some fs types you need the fsync and it's cheap, on others you don't need it and it's costly. The app should not need to modify its behaviour depending on which file system it's running on.
Cheers,
|
|||||||||||||