public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Oester <kernel@linuxace.com>
To: linux-nfs@vger.kernel.org
Subject: NFS "fileid changed" errors since 5.3
Date: Wed, 26 Feb 2020 18:39:14 -0800	[thread overview]
Message-ID: <20200227023914.GC33510@home.linuxace.com> (raw)

When running on 5.3 or 5.4 kernels and mounting a Netapp filer via NFSv3
and accessing the .snapshot directory, "fileid changed" errors appear
in dmesg.  Reverting these 2 patches solves the issue:

eb3d8f42231aec: NFS: Fix inode fileid checks in attribute revalidation code
7e10cc25bfa0dd: NFS: Don't refresh attributes with mounted-on-file information

Various condition checks changed around printing that error in these
commits, but I'm unclear whether the errors are spurious or something
I should actually be concerned about.  Thoughts?

Phil

             reply	other threads:[~2020-02-27  2:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  2:39 Phil Oester [this message]
     [not found] ` <CAN-5tyEN-3x-vEUXvch6Xv_e2x0us2XwVcZGpC4-0vsL2f9n7w@mail.gmail.com>
2020-02-29 17:11   ` NFS "fileid changed" errors since 5.3 Phil Oester

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=20200227023914.GC33510@home.linuxace.com \
    --to=kernel@linuxace.com \
    --cc=linux-nfs@vger.kernel.org \
    /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