From: Andrew Morton <akpm@linux-foundation.org>
To: linux-ext4@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, llowrey@nuclearwinter.com
Subject: Re: [Bugme-new] [Bug 9911] New: fsync blocks concurrent writes to file
Date: Thu, 7 Feb 2008 19:14:10 -0800 [thread overview]
Message-ID: <20080207191410.ed694bab.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9911-10286@http.bugzilla.kernel.org/>
On Thu, 7 Feb 2008 17:40:57 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9911
>
> Summary: fsync blocks concurrent writes to file
> Product: File System
> Version: 2.5
> KernelVersion: 2.6.23.8
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: ext3
> AssignedTo: akpm@osdl.org
> ReportedBy: llowrey@nuclearwinter.com
>
>
> Latest working kernel version: none
> Earliest failing kernel version: 2.6.18
> Distribution: RHEL 4 & Fedora 8
> Hardware Environment: Dual Xeon & dual-core Athlon
> Software Environment: Java 1.5.0_14
> Problem Description: Multiple threads append transactions to a single file.
> When fsyncs are issued, no writes complete until the fsync completes. This has
> the effect of yielding the same write rate regardless of how many threads are
> writing to the file. Solaris 10 does not exhibit this problem and scales well
> as additional threads are added.
>
> I have confirmed this by running strace and witnessing that writes block until
> immediately after the fsync completes.
>
> When using truss on Solaris I have witnessed multiple writes completing while
> an fsync was in progress.
>
> Steps to reproduce:
>
> Open a file for writing.
> Launch multiple threads with each one writing data and followed by an fsync,
> but only if data has been written since the last fsync.
>
>
> I have googled this issue substantially and have found no answers.
>
I supposing teaching java about sync_file_range() would be all too hard.
parent reply other threads:[~2008-02-08 3:13 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-9911-10286@http.bugzilla.kernel.org/>]
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=20080207191410.ed694bab.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=llowrey@nuclearwinter.com \
/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.