From: Chris Mason <mason@suse.com>
To: Peter Zaitsev <peter@mysql.com>
Cc: Hans Reiser <reiser@namesys.com>, Jens Axboe <axboe@suse.de>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: True fsync() in Linux (on IDE)
Date: Fri, 19 Mar 2004 15:23:53 -0500 [thread overview]
Message-ID: <1079727833.11062.200.camel@watt.suse.com> (raw)
In-Reply-To: <1079724411.2576.178.camel@abyss.local>
On Fri, 2004-03-19 at 14:26, Peter Zaitsev wrote:
> On Fri, 2004-03-19 at 05:52, Chris Mason wrote:
>
>
> > I am listening to Peter, Jens and I have spent a significant amount of
> > time on this code. We can go back and spend many more hours testing and
> > debugging the 2.4 changes, or we can go forward with a very nice
> > solution in 2.6.
> >
> > I'm planning on going forward with 2.6
>
> Chris, Hans
>
> It is great to hear this is going to be fixed in 2.6, however it is
> quite a pity we have a real mess with this in 2.4 series.
>
It is indeed.
> Resuming what I've heard so far it looks like it depends on:
>
> - If it is fsync/O_SYNC or O_DIRECT (which user would expect to have
> the same effect in this respect.
> - It depends on kernel version. Some vendors have some fixes, while
> others do not have them.
> - It depends on hardware - if it has write cache on or off
> - It depends on type of write (if it changes mata data or not)
> - Finally it depends on file system and even journal mount options
>
All of the above is correct.
> Just curious does at least Asynchronous IO have the same behavior as
> standard IO ?
>
For the suse patch, yes. If it triggers a commit, you get a cache
flush.
>
> All of these makes it extremely hard to explain what do users need in
> order to get durability for their changes, while preserving performance.
>
> Furthermore as it was broken for years I expect we'll have people which
> developed things with fast fsync() in mind, who would start screaming
> once we have real fsync()
>
> (see my mail about Apple actually disabling cache flush on fsync() due
> to this reason)
These are all difficult issues. I wish I had easier answers for you,
hopefully we can get it all nailed down in 2.6 for starters.
-chris
next prev parent reply other threads:[~2004-03-19 20:22 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 1:08 True fsync() in Linux (on IDE) Peter Zaitsev
2004-03-18 6:47 ` Jens Axboe
2004-03-18 11:34 ` Matthias Andree
2004-03-18 11:55 ` Jens Axboe
2004-03-18 12:21 ` Matthias Andree
2004-03-18 12:37 ` Jens Axboe
2004-03-18 11:58 ` (no subject) Daniel Czarnecki
2004-03-18 19:44 ` True fsync() in Linux (on IDE) Peter Zaitsev
2004-03-18 19:47 ` Jens Axboe
2004-03-18 20:11 ` Chris Mason
2004-03-18 20:17 ` Peter Zaitsev
2004-03-18 20:33 ` Chris Mason
2004-03-18 20:46 ` Peter Zaitsev
2004-03-18 21:02 ` Chris Mason
2004-03-18 21:09 ` Peter Zaitsev
2004-03-18 21:19 ` Chris Mason
2004-03-19 8:05 ` Hans Reiser
2004-03-19 13:52 ` Chris Mason
2004-03-19 19:26 ` Peter Zaitsev
2004-03-19 20:23 ` Chris Mason [this message]
2004-03-19 20:31 ` Hans Reiser
2004-03-19 20:38 ` Chris Mason
2004-03-19 20:48 ` Hans Reiser
2004-03-19 20:56 ` Chris Mason
2004-03-20 11:04 ` Hans Reiser
2004-03-19 19:36 ` Hans Reiser
2004-03-19 19:57 ` Chris Mason
2004-03-19 20:04 ` Hans Reiser
2004-03-19 20:15 ` Chris Mason
2004-03-19 20:06 ` Peter Zaitsev
2004-03-19 22:03 ` Matthias Andree
2004-03-20 10:20 ` Jamie Lokier
2004-03-20 19:48 ` Peter Zaitsev
2004-03-22 13:08 Heikki Tuuri
2004-03-22 13:23 ` Jens Axboe
2004-03-22 15:17 ` Matthias Andree
2004-03-22 15:35 ` Christoph Hellwig
2004-03-22 19:12 ` Christoffer Hall-Frederiksen
2004-03-22 20:28 ` Matthias Andree
2004-03-22 19:33 ` Hans Reiser
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=1079727833.11062.200.camel@watt.suse.com \
--to=mason@suse.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@mysql.com \
--cc=reiser@namesys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).