From: bfields@fieldses.org (J. Bruce Fields)
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
Date: Tue, 26 Feb 2019 14:46:06 -0500 [thread overview]
Message-ID: <20190226194606.GA12035@fieldses.org> (raw)
In-Reply-To: <CADaq8jdp7qVOE9aKui-tgrk00hVmNVXP=yjQ_G-RtGm+G4VrYw@mail.gmail.com>
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.
prev parent reply other threads:[~2019-02-26 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155049372736.14318.3390584694682770373.idtracker@ietfa.amsl.com>
[not found] ` <CADaq8je2Ap4oAZAPOguaWctUs8dQ=Q9g=TO39EOiJW5EJSFTGg@mail.gmail.com>
2019-02-22 23:25 ` file size and getattr Marc Eshel
[not found] ` <CADaq8jfT=nxmVPz4mDRFAaOx36uxWqKbxitqS-YH3GCOs4CsrQ@mail.gmail.com>
2019-02-25 8:49 ` [nfsv4] " Mkrtchyan, Tigran
2019-02-26 2:54 ` Rick Macklem
2019-02-26 3:23 ` Rick Macklem
2019-02-26 12:48 ` Trond Myklebust
2019-02-27 0:13 ` Rick Macklem
2019-02-27 1:12 ` Trond Myklebust
[not found] ` <CADaq8jfcFCuM5u30bXqTvg+0Hc-V+1VO9aUdSJLA090j48LCvA@mail.gmail.com>
2019-02-27 18:05 ` Trond Myklebust
[not found] ` <CADaq8jdp7qVOE9aKui-tgrk00hVmNVXP=yjQ_G-RtGm+G4VrYw@mail.gmail.com>
2019-02-26 19:46 ` J. Bruce Fields [this message]
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=20190226194606.GA12035@fieldses.org \
--to=bfields@fieldses.org \
--cc=davenoveck@gmail.com \
--cc=devel@lists.nfs-ganesha.org \
--cc=linux-nfs-owner@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=tigran.mkrtchyan@desy.de \
/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