Re: Does fsync() block read and write ops on the same file?

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

 



On Fri, Dec 11, 2009 at 11:42:24PM +1100, Dave Chinner wrote:
> No usually - normally only for data writes and metadata
> modifications. However, some filesystems
> dirty objects even on read (e.g. changing atime) and so can
> serialise on other filesystem locks (e.g. ext3 journal lock) that
> is being held by the fsync.

Actually we also take the XFS ilock in shared mode in read, and XFS
takes it in exclusive mode if it has to update filesystem attributes
like the atime.  This might be what Florian is seeing.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[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