Return-Path: linux-nfs-owner@vger.kernel.org Received: from mxout1.mail.janestreet.com ([38.105.200.112]:56249 "EHLO mxout1.mail.janestreet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932160AbbBYVxg (ORCPT ); Wed, 25 Feb 2015 16:53:36 -0500 Received: from tot-qpr-mailcore2.delacy.com ([172.27.56.106] helo=tot-qpr-mailcore2) by mxout1.mail.janestreet.com with smtp (Exim 4.82) (envelope-from ) id 1YQjtf-0007aw-HJ for linux-nfs@vger.kernel.org; Wed, 25 Feb 2015 16:53:35 -0500 Received: from mail-yh0-f52.google.com ([209.85.213.52]) by mxgoog1.mail.janestreet.com with esmtps (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.72) (envelope-from ) id 1YQjtf-0005gY-Ce for linux-nfs@vger.kernel.org; Wed, 25 Feb 2015 16:53:35 -0500 Received: by yhzz6 with SMTP id z6so2473050yhz.13 for ; Wed, 25 Feb 2015 13:53:35 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Chris Perl Date: Wed, 25 Feb 2015 16:53:14 -0500 Message-ID: Subject: Re: File Read Returns Non-existent Null Bytes To: Trond Myklebust Cc: Linux NFS Mailing List , Chris Perl Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: > There is nothing to fix. The close-to-open cache consistency model is > clear that your applications must not access a file that is being > modified on another client or on the server. Ok, thanks for helping me understand this a little more clearly. For my own edification, is there somewhere I can find the details where these things are spelled out (or is it just somewhere in rfc1813 that I haven't seen)?