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?

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

Thanks for any/all feedback on this front!


-----Original Message-----
From: J. Bruce Fields [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 22, 2007 4:27 PM
To: Morrison, Tom
Cc: [EMAIL PROTECTED]; linux-kernel@vger.kernel.org; Rushton,
Matt
Subject: Re: NFS/RPC Hangs after updating time...

On Wed, Aug 22, 2007 at 02:37:22PM -0400, Morrison, Tom wrote:
> I am working with a 2.6.11++ kernel on an embedded 
> server platform that is NFS serving Linux rootfs 
> for other embedded NFS Client boards.
> 
> Everything works fine when the system time on the 
> server board is relatively synchronized with the real-time. 
> 
> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to