From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Morrison, Tom" <tmorrison@empirix.com>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Follow up to: NFS/RPC Hangs after updating time...
Date: Fri, 31 Aug 2007 17:45:51 -0400 [thread overview]
Message-ID: <20070831214551.GP11165@fieldses.org> (raw)
In-Reply-To: <BD261180E6D35F4D9D32F3E44FD3D901091DE759@EMPBEDEX.empirix.com>
On Fri, Aug 31, 2007 at 02:35:19PM -0400, Morrison, Tom wrote:
> This is a follow-up...
>
> After a huge pain in the rear upgrading from a
> 2.6.11++ to a 2.6.23-rc3 (I'll give the powerpc
> folks a 'piece' of my mind on that front) - the
> NFS hang problem that I was experiencing on the
> older kernel is NOT occurring on this new version.
>
> Now what do I do?
Well, between the time jump and the rpc debugging output, you've got
some great clues there--given some time I'm sure it would be possible to
completely figure out what's going on.
Unfortunately the people with the most knowledge of the code probably
don't have the time to fix problems on old kernels, so unless somebody
else recognizes the problem immediately, I'm not sure what to suggest.
Obviously, a wholesale upgrade to a more recent kernel would be the one
sure bet....
> Is the net/sunrpc net/nfsx pieces isolated enough
> from the rest of the kernel that I could fork-lift
> it back to the 2.6.11 (or is that really a lost cause).
I suspect it's a lost cause. A lot has happened in the last couple
years.
--b.
> > It hangs after attempting to update the time from a
> > nonsensical time (e.g.: 2 months ago) - the most significant
> > part of it is that it only hangs IFF it has started
> > serving its NFS client boards before I attempt to
> > update the time.
> >
> >
> > The most significant output (when turning on
> > RPC debugging) is from:
> >
> > linux/net/sunrpc/cache.c (cache_check) - line 90:
> >
> > >> Want update, refage=1800, age=4288285
> >
> > It continually loops through this method - and the cache
> > never gets updated...even thought with some additional
> > sleuthing (aka: additional debug printks - it thinks
> > that there is an cache update pending).
>
> Can you reproduce the problem with the current kernel? (Say 2.6.22 or
> later?)
>
> --b.
prev parent reply other threads:[~2007-08-31 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 18:37 Morrison, Tom
2007-08-22 20:26 ` J. Bruce Fields
2007-08-31 18:35 ` Follow up to: " Morrison, Tom
2007-08-31 21:45 ` J. Bruce Fields [this message]
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=20070831214551.GP11165@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=tmorrison@empirix.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
all inboxes | Powered by JetHome®