From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS: server error: fileid changed
Date: Sun, 28 Nov 2010 13:19:43 -0500 [thread overview]
Message-ID: <20101128181942.GA23535@fieldses.org> (raw)
In-Reply-To: <alpine.LNX.2.01.1011281853520.7586@obet.zrqbmnf.qr>
On Sun, Nov 28, 2010 at 06:56:37PM +0100, Jan Engelhardt wrote:
>
> On Sunday 2010-11-28 17:05, J. Bruce Fields wrote:
> >On Sun, Nov 28, 2010 at 03:23:23PM +0100, Jan Engelhardt wrote:
> >> Sometime between 2.6.33 and 2.6.36 it seems, knfsd has become really
> >> unreliable, having clients start to emit messages like
> >>
> >> (nfsv3)
> >> [42306.521225] NFS: server nova error: fileid changed
> >> [42306.521226] fsid 0:10: expected fileid 0x1b007be, got 0x1b006b0
> >>
> >> On nfsv4, it is even worse, as updates on the server are not immediately
> >> reflected on the client like it was the case on nfsv3.
> >> Unfortunately, that is all the information I currently have.
> >> (Server is on 2.6.36-rc8, client on 2.6.37-rc1.)
> >
> >Have you really being changing only the server, or have you been
> >changing the client at the same time?
> >
> >See e.g.
> > http://marc.info/?l=linux-nfs&m=129088225122788&w=2
>
> For my definition of not touching the server yes. (There may be
> atime updates, but that's about it.)
I was asking about kernel versions; so:
client 2.6.37-rc1, server 2.6.33
worked, but
client 2.6.37-rc1, server 2.6.36-rc8
didn't?
It would be worth trying the most recent client patches anyway, as your
symptoms look suspiciously similar to those reported recently, and we'd
like to rule out the known 2.6.37-rc1 client bugs.
What filesystem are you exporting?
--b.
next prev parent reply other threads:[~2010-11-28 18:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 14:23 NFS: server error: fileid changed Jan Engelhardt
2010-11-28 16:05 ` J. Bruce Fields
2010-11-28 17:56 ` Jan Engelhardt
2010-11-28 18:19 ` J. Bruce Fields [this message]
2010-12-05 14:41 ` Jan Engelhardt
2010-12-06 16:17 ` J. Bruce Fields
2011-01-30 13:27 ` Jan Engelhardt
2011-01-31 15:40 ` 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=20101128181942.GA23535@fieldses.org \
--to=bfields@fieldses.org \
--cc=jengelh@medozas.de \
--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).