From: Peter Staubach <staubach@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: Data coherency trouble with multiple clients on2.6.14-rc5
Date: Mon, 07 Nov 2005 11:52:04 -0500 [thread overview]
Message-ID: <436F8634.5020007@redhat.com> (raw)
In-Reply-To: <044B81DE141D7443BCE91E8F44B3C1E288E5F2@exsvl02.hq.netapp.com>
Lever, Charles wrote:
>>On Mon, 2005-11-07 at 08:08 -0800, Lever, Charles wrote:
>>
>>
>>
>>>in the case of "noac", OTW writes are always synchronous. thus you
>>>should never have the problem where concurrent async writes
>>>
>>>
>>will obscure
>>
>>
>>>server-side changes on "noac" mounts.
>>>
>>>
>>However reads are not synchronous, nor are they ordered. You have no
>>guarantee that the RPC READ call that filled the first page
>>you read was
>>handled by the server before the read that filled the next page.
>>
>>
>
>yes, but the client can make use of WCC in the case where it's own
>updates are always synchronous, right?
>
As long as the writes are synchronous with respect to the system call
and there
is no sharing going on, ie. two processes reading or writing at the same
time.
Thanx...
ps
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-11-07 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-07 16:47 Data coherency trouble with multiple clients on2.6.14-rc5 Lever, Charles
2005-11-07 16:52 ` Peter Staubach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 15:27 Data coherency trouble with multiple clients, on2.6.14-rc5 Lever, Charles
2005-10-26 16:50 ` Trond Myklebust
2005-10-26 18:45 ` Peter Staubach
2005-10-26 19:08 ` Trond Myklebust
2005-10-26 19:53 ` Peter Staubach
2005-10-26 21:05 ` Trond Myklebust
2005-10-26 21:22 ` Peter Staubach
2005-10-26 21:57 ` Trond Myklebust
2005-10-27 12:25 ` Peter Staubach
2005-10-27 12:53 ` Trond Myklebust
2005-10-27 14:25 ` Calum Mackay
2005-10-27 15:33 ` Trond Myklebust
2005-10-26 6:01 Data coherency trouble with multiple clients, on 2.6.14-rc5 Charles Duffy
2005-10-26 6:23 ` Trond Myklebust
2005-10-26 7:25 ` Data coherency trouble with multiple clients, on2.6.14-rc5 Charles Duffy
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=436F8634.5020007@redhat.com \
--to=staubach@redhat.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.