From: Chuck Lever <chuck.lever@oracle.com>
To: Wim Colgate <Wim.Colgate@xensource.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS_UNSTABLE vs. FILE and DATA sync.
Date: Mon, 06 Aug 2007 13:10:22 -0400 [thread overview]
Message-ID: <46B755FE.1010909@oracle.com> (raw)
In-Reply-To: <46B74E5C.4060400@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Chuck Lever wrote:
> Wim Colgate wrote:
>> If I have a soft mount, and open a file with O_DIRECT and O_SYNC,
>> should I ever expect a callback (nfs_writeback_done) with a successful
>> task->tk_status (i.e >= 0) with the committed state
>> (resp->verf->committed) set to NFS_UNSTABLE?
>
> Yes, this can happen if the server decides to return NFS_UNSTABLE. Rare,
> but possible.
Let me be more clear about this.
O_DIRECT and O_SYNC determine client behavior only. However, they don't
necessarily force NFS_FILE_SYNC writes all the time. For example, if an
application issues a direct write request that is much larger than the
current wsize, the Linux NFS client will send the write using
NFS_UNSTABLE requests followed by a COMMIT. That makes it easier for
the server to schedule disk writes more efficiently.
>> A secondary question: if the above is expected, does this occur
>> because someone is caching the write and is there a mechanism to
>> disable this effect?
>
> Servers can return NFS_UNSTABLE to any WRITE request, so I can't think
> of a way this might be disabled.
Even though an NFS client requests an NFS_FILE_SYNC write, the server
still has the choice of returning something less, even NFS_UNSTABLE. In
general that's a rare occurrence, but is something I've seen in practice.
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-06 17:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 16:02 NFS_UNSTABLE vs. FILE and DATA sync Wim Colgate
2007-08-06 16:37 ` Chuck Lever
2007-08-06 17:10 ` Chuck Lever [this message]
2007-08-06 18:58 ` Trond Myklebust
2007-08-06 19:13 ` Chuck Lever
2007-08-06 19:19 ` Trond Myklebust
2007-08-06 19:35 ` Chuck Lever
2007-08-06 17:33 ` Peter Staubach
2007-08-06 17:40 ` Wim Colgate
2007-08-06 19:16 ` Chuck Lever
2007-08-06 19:33 ` Wim Colgate
2007-08-06 19:42 ` Chuck Lever
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=46B755FE.1010909@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Wim.Colgate@xensource.com \
--cc=nfs@lists.sourceforge.net \
/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