Date:   Tue, 26 Feb 2019 14:46:06 -0500
To:     David Noveck <davenoveck@gmail.com>
Cc:     "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>,
        linux-nfs-owner <linux-nfs-owner@vger.kernel.org>,
        linux-nfs <linux-nfs@vger.kernel.org>, NFSv4 <nfsv4@ietf.org>,
        Ganesha-devel <devel@lists.nfs-ganesha.org>
Subject: Re: [nfsv4] file size and getattr
Message-ID: <20190226194606.GA12035@fieldses.org>
References: <155049372736.14318.3390584694682770373.idtracker@ietfa.amsl.com>
 <CADaq8je2Ap4oAZAPOguaWctUs8dQ=Q9g=TO39EOiJW5EJSFTGg@mail.gmail.com>
 <OFE5A6CD32.4DC48078-ON882583A9.007FB4BC-882583A9.0080ACAC@notes.na.collabserv.com>
 <CADaq8jfT=nxmVPz4mDRFAaOx36uxWqKbxitqS-YH3GCOs4CsrQ@mail.gmail.com>
 <741516773.7109032.1551084577150.JavaMail.zimbra@desy.de>
 <CADaq8jdp7qVOE9aKui-tgrk00hVmNVXP=yjQ_G-RtGm+G4VrYw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CADaq8jdp7qVOE9aKui-tgrk00hVmNVXP=yjQ_G-RtGm+G4VrYw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Mon, Feb 25, 2019 at 10:50:21AM -0500, David Noveck wrote:
> For example, if you (or another client) read data written unstably,
> and there was been no restart you will see bytes past the eof as known
> by the metadata server.

Possibly worth noting that if there *is* a restart, all bets are off.

And how do you know there hasn't been a restart?  Or if you can figure
that out (e.g. if you're using sessions), how do you know when clients
have finished retransmitting unstable write data?

I'd be curious what prompted the original question.

--b.