From: Florian Weimer <fweimer@bfk.de>
To: linux-fsdevel@vger.kernel.org
Subject: Does fsync() block read and write ops on the same file?
Date: Thu, 10 Dec 2009 09:22:35 +0000 [thread overview]
Message-ID: <82ein3npyc.fsf@mid.bfk.de> (raw)
I've got an odd performance issue. It seems that when fsync() is
called on a file, other processes block when they try to access it.
This is not merely due to I/O contention on the underlying block
device, it seems.
Oracle reported a similar performance issue in the Berkeley DB JE
changelog. Is this really true? Are there any workarounds? (I'm
mainly interested in the situation on ext[34] and XFS.)
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-12-10 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 9:22 Florian Weimer [this message]
2009-12-11 3:55 ` Does fsync() block read and write ops on the same file? Dave Chinner
2009-12-11 8:53 ` Florian Weimer
2009-12-11 12:42 ` Dave Chinner
2009-12-11 12:53 ` Florian Weimer
2009-12-12 23:05 ` Dave Chinner
2009-12-11 13:21 ` Christoph Hellwig
2009-12-11 13:35 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82ein3npyc.fsf@mid.bfk.de \
--to=fweimer@bfk.de \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.