From: Trond Myklebust <trondmy@hammerspace.com>
To: "davenoveck@gmail.com" <davenoveck@gmail.com>,
"tigran.mkrtchyan@desy.de" <tigran.mkrtchyan@desy.de>,
"rmacklem@uoguelph.ca" <rmacklem@uoguelph.ca>
Cc: "devel@lists.nfs-ganesha.org" <devel@lists.nfs-ganesha.org>,
"linux-nfs-owner@vger.kernel.org"
<linux-nfs-owner@vger.kernel.org>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"nfsv4@ietf.org" <nfsv4@ietf.org>
Subject: Re: [nfsv4] file size and getattr
Date: Tue, 26 Feb 2019 12:48:28 +0000 [thread overview]
Message-ID: <1cbdd04ce23c5012f59b6d5dcbb6b505be0675b9.camel@hammerspace.com> (raw)
In-Reply-To: <QB1PR01MB3537215D010370E139D70843DD7B0@QB1PR01MB3537.CANPRD01.PROD.OUTLOOK.COM>
Hi Rick,
On Tue, 2019-02-26 at 03:23 +0000, Rick Macklem wrote:
>
> If I recall correctly, the Linux client only did LayoutCommits after
> Commits.
> As such, no LayoutCommit were done after writes to a DS that were
> FILE_SYNC
> (or stable, if you prefer). Without the LayoutCommit, the pNFS server
> didn't
> know when it needed to get an up to date size.
> The FreeBSD client does a LayoutCommit after writing to a DS whenever
> it is done
> writing, such as an fsync() or close() syscall on the file or an
> unlock of a write lock
> on the file.
>
Please see the Errata ID 2751 http://www.rfc-editor.org/errata/eid2751
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-02-26 12:49 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 [this message]
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
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=1cbdd04ce23c5012f59b6d5dcbb6b505be0675b9.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--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=rmacklem@uoguelph.ca \
--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