fsync() after close() and re-open -- insights appreciated

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

here's a simple question I'm having trouble finding answers to that is
probably trivial to answer for file system developers.

Does a sequence of close()/re-open()/fsync() provide the same durability
guarantees as fsync()/close()?

http://pubs.opengroup.org/onlinepubs/009695399/functions/fsync.html
specifies that

  "The fsync() function shall request that all data for the open file
descriptor named by fildes is to be transferred to the storage device"

which seems to restrict the statement to "for the open file descriptor",
possibly suggesting that close()/open()/fsync() may not have the desired
effect.

Being able to link to an authorative answer would be very appreciated.

Thanks,
Niklas



[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux