From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>,
sfaibish <sfaibish@emc.com>
Subject: Re: fileid changed
Date: Tue, 16 Nov 2010 13:27:04 -0500 [thread overview]
Message-ID: <20101116182703.GB3971@fieldses.org> (raw)
In-Reply-To: <20101115201000.GC31906@merit.edu>
On Mon, Nov 15, 2010 at 03:10:00PM -0500, Jim Rees wrote:
> Jim Rees wrote:
>
> With Benny's pnfs-all-latest kernel of this morning I'm getting this:
>
> NFS: server emc-1 error: fileid changed
> fsid 0:14: expected fileid 0x4c1b59f7, got 0x167
> NFS: server emc-1 error: fileid changed
> fsid 0:14: expected fileid 0x4c891415, got 0x174
> NFS: server emc-1 error: fileid changed
> fsid 0:14: expected fileid 0x174, got 0x4c891415
> NFS: server emc-1 error: fileid changed
> fsid 0:14: expected fileid 0x177, got 0x4ce18474
> [ followed by many similar lines ]
Naively, it sounds like the server is returning different fileid's for
getattr's on the same filehandle? Sounds like a definite server
bug--might be worth looking at a trace to confirm that, though.
--b.
>
> This happens during test5: read and write of Connectathon basic, pnfs block
> layout client, EMC server. The user process hangs at this point, no oops.
> I can provide more details if needed. This could easily be my screw-up of
> course, but I haven't changed anything in my code and I wasn't getting this
> with the previous kernel.
>
> Sorry, I was mistaken. I was getting this with the previous kernel as
> well. I'm still interested to know if anyone recognizes this.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-16 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 19:15 fileid changed Jim Rees
2010-11-15 20:10 ` Jim Rees
2010-11-16 18:27 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 20:48 Jim Rees
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=20101116182703.GB3971@fieldses.org \
--to=bfields@fieldses.org \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
--cc=sfaibish@emc.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).