Linux NFS development
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "Lever, Charles" <Charles.Lever@netapp.com>,
	Charles Duffy <ccd@mailcall.com.au>,
	nfs@lists.sourceforge.net
Subject: Re: Data coherency trouble with multiple clients,	on2.6.14-rc5
Date: Wed, 26 Oct 2005 14:45:35 -0400	[thread overview]
Message-ID: <435FCECF.2090800@redhat.com> (raw)
In-Reply-To: <1130345451.8852.7.camel@lade.trondhjem.org>

Trond Myklebust wrote:

>on den 26.10.2005 klokka 08:27 (-0700) skreiv Lever, Charles:
>
>  
>
>>i agree that O_DIRECT is the right solution.  however, even with "noac"
>>i would expect mr. duffy's workload to behave correctly most of the
>>time.  sounds like he is able to make it fail very easily.
>>    
>>
>
>Why would you expect that?
>
>"noac" does not turn off data caching, nor does it change the policy
>that the client will not invalidate the data cache while it is holding
>the file open for write.
>

It seems to me that the policy should be to allow cache 
validation/invalidation
unless the file is mmap'd for writing or if there are active WRITEs 
outstanding.
Simply having the file open for write should not affect the consistency 
model.

    Thanx...

       ps


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-10-26 18:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2005-11-07 16:47 Data coherency trouble with multiple clients on2.6.14-rc5 Lever, Charles
2005-11-07 16:52 ` Peter Staubach
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=435FCECF.2090800@redhat.com \
    --to=staubach@redhat.com \
    --cc=Charles.Lever@netapp.com \
    --cc=ccd@mailcall.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox