From: Simon Kirby <sim@hostway.ca>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS client/sunrpc getting stuck on 2.6.36
Date: Tue, 23 Nov 2010 21:18:55 -0800 [thread overview]
Message-ID: <20101124051855.GA22114@hostway.ca> (raw)
In-Reply-To: <1290369260.5481.18.camel@heimdal.trondhjem.org>
On Sun, Nov 21, 2010 at 02:54:20PM -0500, Trond Myklebust wrote:
> > [219158.456270] NFS: server 10.10.52.230 error: fileid changed
> > [219158.456273] fsid 0:4e: expected fileid 0x57bcf57c, got 0x57bd5442
> >
> > Finally, on the last one I had remounted all of the NFS mount points with
> > that option, and there have been no errors since.
>
> I just posted 8 patches to fix up bugs and regressions in the readdir
> code. Can you try with some of these?
2.6.37-rc3 plus those 8 patches was running on one box for just over a
day when it just crashed for some reason (got rebooted before I could see
the console). Anyway, while it was running, it was still logging "fileid
changed" lines as before:
[84197.182497] NFS: server 10.10.52.228 error: fileid changed
[84197.182499] fsid 0:47: expected fileid 0x96fe0343, got 0x4926a389
[85226.297721] NFS: server 10.10.52.227 error: fileid changed
[85226.297724] fsid 0:39: expected fileid 0x254d3a97, got 0x480014a6
Simon-
next prev parent reply other threads:[~2010-11-24 5:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 2:35 NFS client/sunrpc getting stuck on 2.6.36 Simon Kirby
2010-11-11 5:22 ` Trond Myklebust
2010-11-11 8:49 ` Simon Kirby
2010-11-19 20:20 ` Simon Kirby
2010-11-19 21:24 ` Trond Myklebust
2010-11-19 22:03 ` Simon Kirby
2010-11-19 22:17 ` Trond Myklebust
2010-11-19 22:58 ` Simon Kirby
2010-11-19 23:17 ` Trond Myklebust
2010-11-21 6:43 ` Simon Kirby
2010-11-21 19:55 ` Trond Myklebust
2010-11-21 6:40 ` Simon Kirby
2010-11-21 19:54 ` Trond Myklebust
2010-11-24 5:18 ` Simon Kirby [this message]
2010-11-24 15:05 ` Trond Myklebust
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=20101124051855.GA22114@hostway.ca \
--to=sim@hostway.ca \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.