From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: Data coherency trouble with multiple
	clients,	on2.6.14-rc5
Date: Wed, 26 Oct 2005 15:08:13 -0400
Message-ID: <1130353693.8859.21.camel@lade.trondhjem.org>
References: <044B81DE141D7443BCE91E8F44B3C1E288E5A5@exsvl02.hq.netapp.com>
	 <1130345451.8852.7.camel@lade.trondhjem.org>  <435FCECF.2090800@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Cc: "Lever, Charles" <Charles.Lever@netapp.com>,
	Charles Duffy <ccd@mailcall.com.au>, nfs@lists.sourceforge.net
To: Peter Staubach <staubach@redhat.com>
In-Reply-To: <435FCECF.2090800@redhat.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

on den 26.10.2005 klokka 14:45 (-0400) skreiv Peter Staubach:

> 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.

That is what we did for 2.4.x, but what kind of extra guarantees does
that really bring you? You cannot actually rely on it to provide
stronger caching semantics than the close-to-open case.

Cheers,
  Trond


-------------------------------------------------------
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