From: "Theodore Ts'o" <tytso@mit.edu>
To: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: ext3 and SPEC SFS Run rules.
Date: Mon, 26 Jul 2004 15:57:16 -0400 [thread overview]
Message-ID: <20040726195716.GB8144@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0407261010400.32233-100000@localhost.localdomain>
On Mon, Jul 26, 2004 at 10:12:01AM +0100, Tigran Aivazian wrote:
> On Mon, 26 Jul 2004, Andrew Morton wrote:
> > ext3 should be fully syncing data and metadata for both fsync() and O_SYNC
> > writes in all three journalling modes. If not, that's a big bug.
>
> Ok, so, can I conclude that you are therefore saying that ext3 (with
> default mount options) is compliant with SPEC SFS Run rules wrt NFS
> protocol requirements:
This is up to the NFS server, not to the underlying filesystem. It
would be insane for every single local write() to have mandatory
O_SYNC semantics, even if it is required by the NFS protocol.
In modern Linux implementations of the NFS server, you can specify
whether or not the synchronization semantics as demanded by the NFS
protocol, or whether the more relaxed async writebacks are done.
Obviously, this has some pretty serious performance vs robustness
implications.
- Ted
next prev parent reply other threads:[~2004-07-26 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 18:49 ext3 and SPEC SFS Run rules Tigran Aivazian
2004-07-26 7:03 ` Andrew Morton
2004-07-26 9:12 ` Tigran Aivazian
2004-07-26 9:18 ` Tigran Aivazian
2004-07-28 21:00 ` Andreas Dilger
2004-07-26 19:57 ` Theodore Ts'o [this message]
2004-07-26 20:01 ` Andrew Morton
2004-07-26 23:00 ` Neil Brown
2004-07-26 23:45 ` Brian Pawlowski
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=20040726195716.GB8144@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@aivazian.fsnet.co.uk \
/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.