linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: linux-nfs@vger.kernel.org
Cc: peter honeyman <honey@citi.umich.edu>, sfaibish <sfaibish@emc.com>
Subject: Re: fileid changed
Date: Mon, 15 Nov 2010 15:10:00 -0500	[thread overview]
Message-ID: <20101115201000.GC31906@merit.edu> (raw)
In-Reply-To: <20101115191533.GA31837@merit.edu>

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 ]
  
  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.

  reply	other threads:[~2010-11-15 20:10 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 [this message]
2010-11-16 18:27   ` J. Bruce Fields
  -- 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=20101115201000.GC31906@merit.edu \
    --to=rees@umich.edu \
    --cc=honey@citi.umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --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).