From: Jim Rees <rees@umich.edu>
To: linux-nfs@vger.kernel.org
Cc: peter honeyman <honey@citi.umich.edu>
Subject: fileid changed
Date: Wed, 19 Jan 2011 15:48:20 -0500 [thread overview]
Message-ID: <20110119204820.GA8471@merit.edu> (raw)
I'm getting fresh reports of "fileid changed" with Benny's latest
pnfs-all-latest. This is x86_64 4.1 non-pnfs client against EMC Celerra
server. I'm getting a tcpdump now. The kernel does have the
nfs_same_file() fix that Trond sent in November.
NFS: server 10.244.76.184 error: fileid changed
fsid 0:15: expected fileid 0x19, got 0x4d0000fb
NFS: server 10.244.76.184 error: fileid changed
fsid 0:15: expected fileid 0x1b, got 0x4d00047c
NFS: server 10.244.76.184 error: fileid changed
fsid 0:15: expected fileid 0x1a, got 0x4d00047c
NFS: server 10.244.76.184 error: fileid changed
fsid 0:15: expected fileid 0x1c, got 0x4d00047f
NFS: server 10.244.76.184 error: fileid changed
fsid 0:15: expected fileid 0x1d, got 0x4d000481
next reply other threads:[~2011-01-19 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 20:48 Jim Rees [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-15 19:15 fileid changed Jim Rees
2010-11-15 20:10 ` Jim Rees
2010-11-16 18:27 ` 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=20110119204820.GA8471@merit.edu \
--to=rees@umich.edu \
--cc=honey@citi.umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).