From: Greg Lindahl Subject: Re: Re: NFS as a Cluster File System. Date: Fri, 10 Jan 2003 09:38:20 -0800 Sender: nfs-admin@lists.sourceforge.net Message-ID: <20030110173820.GA3066@wumpus.attbi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net, linux-ha@muc.de Return-path: Received: from 12-234-28-98.client.attbi.com ([12.234.28.98] helo=localhost.localdomain) by sc8-sf-list1.sourceforge.net with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.31-VA-mm2 #1 (Debian)) id 18X33l-0002QI-00 for ; Fri, 10 Jan 2003 09:35:09 -0800 To: Trond Myklebust In-Reply-To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: > > I think this can be resolved with the "noac" mount option > > (prior to V4). > > Nope. It can only be resolved using file locking. There are 2 consistency problems: metadata and data. Metadata is solved by noac. And yes, some MPI programs do things like "node 0 writes out a bunch of files, then tells all the other nodes to read one file each." This means that you have about 1/100 of a second window between creation on one client and reading on a different client. Data consistency is solved by file locking. -- greg ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs