From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v4 24/28] NFS: Getattr doesn't require data sync semantics
Date: Sun, 17 Jul 2016 20:48:47 -0700 [thread overview]
Message-ID: <20160718034847.GA1195@infradead.org> (raw)
In-Reply-To: <1467844205-76852-25-git-send-email-trond.myklebust@primarydata.com>
On Wed, Jul 06, 2016 at 06:30:01PM -0400, Trond Myklebust wrote:
> When retrieving stat() information, NFS unfortunately does require us to
> sync writes to disk in order to ensure that mtime and ctime are up to
> date. However we shouldn't have to ensure that those writes are persisted.
>
> Relaxing that requirement does mean that we may see an mtime/ctime change
> if the server reboots and forces us to replay all writes.
>
> The exception to this rule are pNFS clients that are required to send
> layoutcommit, however that is dealt with by the call to pnfs_sync_inode()
> in _nfs_revalidate_inode().
This one breaks xfstests generic/207 on block/scsi layout for me. The
reason for that is that we need a layoutcommit after writing out all
data for the file for the file size to be updated on the server.
Below is my attempt to fix this by re-adding pnfs_sync_inode to
nfs_getattr. The call in _nfs_revalidate_inode isn't enough as it
doesn't get called in most cases we care about.
diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
index 22a53ee..8bd04cf 100644
--- a/fs/nfs/inode.c
+++ b/fs/nfs/inode.c
@@ -660,11 +660,20 @@ int nfs_getattr(struct vfsmount *mnt, struct dentry *dentry, struct kstat *stat)
int err = 0;
trace_nfs_getattr_enter(inode);
- /* Flush out writes to the server in order to update c/mtime. */
+
+ /*
+ * Flush out writes to the server in order to update c/mtime as well
+ * as the file size. In the pNFS case this also requires a
+ * LAYOUTCOMMIT.
+ */
if (S_ISREG(inode->i_mode)) {
err = filemap_write_and_wait(inode->i_mapping);
if (err)
goto out;
+
+ err = pnfs_sync_inode(inode, true);
+ if (err)
+ goto out;
}
/*
next prev parent reply other threads:[~2016-07-18 3:48 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:29 [PATCH v4 00/28] NFS writeback performance patches for v4.8 Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 01/28] NFS: Don't flush caches for a getattr that races with writeback Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 02/28] NFS: Cache access checks more aggressively Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 03/28] NFS: Cache aggressively when file is open for writing Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 04/28] NFS: Kill NFS_INO_NFS_INO_FLUSHING: it is a performance killer Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 05/28] NFS: writepage of a single page should not be synchronous Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 06/28] NFS: Don't hold the inode lock across fsync() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 07/28] NFS: Don't call COMMIT in ->releasepage() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 08/28] pNFS/files: Fix layoutcommit after a commit to DS Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 09/28] pNFS/flexfiles: " Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 10/28] pNFS/flexfiles: Clean up calls to pnfs_set_layoutcommit() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 11/28] pNFS: Files and flexfiles always need to commit before layoutcommit Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 12/28] pNFS: Ensure we layoutcommit before revalidating attributes Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 13/28] pNFS: pnfs_layoutcommit_outstanding() is no longer used when !CONFIG_NFS_V4_1 Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 14/28] NFS: Fix O_DIRECT verifier problems Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 15/28] NFS: Ensure we reset the write verifier 'committed' value on resend Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 16/28] NFS: Remove racy size manipulations in O_DIRECT Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 17/28] NFS Cleanup: move call to generic_write_checks() into fs/nfs/direct.c Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 18/28] NFS: Move buffered I/O locking into nfs_file_write() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 19/28] NFS: Do not serialise O_DIRECT reads and writes Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 20/28] NFS: Cleanup nfs_direct_complete() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 21/28] NFS: Remove redundant waits for O_DIRECT in fsync() and write_begin() Trond Myklebust
2016-07-06 22:29 ` [PATCH v4 22/28] NFS: Remove unused function nfs_revalidate_mapping_protected() Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 23/28] NFS: Do not aggressively cache file attributes in the case of O_DIRECT Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 24/28] NFS: Getattr doesn't require data sync semantics Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 25/28] NFSv4.2: Fix a race in nfs42_proc_deallocate() Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 26/28] NFSv4.2: Fix writeback races in nfs4_copy_file_range Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 27/28] NFSv4.2: llseek(SEEK_HOLE) and llseek(SEEK_DATA) don't require data sync Trond Myklebust
2016-07-06 22:30 ` [PATCH v4 28/28] NFS nfs_vm_page_mkwrite: Don't freeze me, Bro Trond Myklebust
2016-07-18 3:48 ` Christoph Hellwig [this message]
2016-07-18 4:32 ` [PATCH v4 24/28] NFS: Getattr doesn't require data sync semantics Trond Myklebust
2016-07-18 4:59 ` Trond Myklebust
2016-07-19 3:58 ` hch
2016-07-19 20:00 ` [PATCH v4 24/28] " Benjamin Coddington
2016-07-19 20:06 ` Trond Myklebust
2016-07-20 15:03 ` Benjamin Coddington
2016-07-21 8:22 ` hch
2016-07-21 8:32 ` Benjamin Coddington
2016-07-21 9:10 ` Benjamin Coddington
2016-07-21 9:52 ` Benjamin Coddington
2016-07-21 12:46 ` Trond Myklebust
2016-07-21 13:05 ` Benjamin Coddington
2016-07-21 13:20 ` Trond Myklebust
2016-07-21 14:00 ` Trond Myklebust
2016-07-21 14:02 ` Benjamin Coddington
2016-07-25 16:26 ` Benjamin Coddington
2016-07-25 16:39 ` Trond Myklebust
2016-07-25 18:26 ` Benjamin Coddington
2016-07-25 18:34 ` Trond Myklebust
2016-07-25 18:41 ` Benjamin Coddington
2016-07-26 16:32 ` Benjamin Coddington
2016-07-26 16:35 ` Trond Myklebust
2016-07-26 17:57 ` Benjamin Coddington
2016-07-26 18:07 ` Trond Myklebust
2016-07-27 11:55 ` Benjamin Coddington
2016-07-27 12:15 ` Trond Myklebust
2016-07-27 12:31 ` Trond Myklebust
2016-07-27 16:14 ` Benjamin Coddington
2016-07-27 18:05 ` Trond Myklebust
2016-07-28 9:47 ` Benjamin Coddington
2016-07-28 12:31 ` Trond Myklebust
2016-07-28 14:04 ` Trond Myklebust
2016-07-28 15:38 ` Benjamin Coddington
2016-07-28 15:39 ` Trond Myklebust
2016-07-28 15:33 ` Benjamin Coddington
2016-07-28 15:36 ` Trond Myklebust
2016-07-28 16:40 ` Benjamin Coddington
2016-07-28 16:41 ` Trond Myklebust
2016-07-19 20:09 ` Benjamin Coddington
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=20160718034847.GA1195@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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;
as well as URLs for NNTP newsgroup(s).