public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Hughes <doug@will.to>
To: John Stoffel <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange linux kernel NFS problem(s)
Date: Fri, 03 Dec 2010 13:47:43 -0500	[thread overview]
Message-ID: <4CF93B4F.20506@will.to> (raw)
In-Reply-To: <19705.10909.860332.657164@quad.stoffel.home>

>>>>>> "Doug" == Doug Hughes<doug@will.to>  writes:
> Doug>  So, this is my first post, but not my first problem of this
> Doug>  nature. It just so happens that this is the first one with a
> Doug>  recent kernel to give useful data, useful enough to post it and
> Doug>  seek some advice on the subject:
>
> kernel 2.6.34 is still pretty old, and there have been lots of NFS
> fixes.  Can you upgrade to something newer as a test?  Also, what
> distro are you using?
>
> Is this an NFS client or the NFS server which is crapping out?  More
> details please...
>
>
It wasn't very old when we started testing it to resolve further NFS 
problems about 6 weeks ago. It takes a while to get through the 
necessary regressions to make sure things are generally ok before 
getting comfortable with a rollout to more than a couple nodes. The 
problems we experience are more of a statistical nature across nodes, so 
we don't usually experience them until we have some mass of upgraded nodes.

We checked through the changelists and didn't see anything that stood 
out as "ah ha, that's the problem". Most of the updates seemed to not 
mention NFS at all. Do you have one a particular issue/patch in mind?

This is a NFS client mounting a server elsewhere. The ps listing shows 
several stuck mount commands, which is another symptom of the general 
issue. Let me know what else. Certainly it's possible to try another, 
new kernel, but then I'll be posting about .36.1 in about 6-9 weeks and 
chances are that it will be considered old. :\

Distro is Centos5.4 with updates. kernel is from kernel.org


      reply	other threads:[~2010-12-03 18:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03  2:40 strange linux kernel NFS problem(s) Doug Hughes
2010-12-03 17:36 ` John Stoffel
2010-12-03 18:47   ` Doug Hughes [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=4CF93B4F.20506@will.to \
    --to=doug@will.to \
    --cc=john@stoffel.org \
    --cc=linux-kernel@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