From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Brian D. McGrew" <brian@visionpro.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Stale NFS File Handle
Date: Fri, 03 Feb 2006 14:09:04 -0500 [thread overview]
Message-ID: <1138993744.7861.18.camel@lade.trondhjem.org> (raw)
In-Reply-To: <14CFC56C96D8554AA0B8969DB825FEA0970A93@chicken.machinevisionproducts.com>
On Fri, 2006-02-03 at 10:05 -0800, Brian D. McGrew wrote:
> Good morning all (kind of a long winded mail, please have patience!)
>
> I've got an FC3 server running a 2.6.9 kernel and sharing about 500GB of
> disk space on a RAID5 array via NFS. This box has been running fine for
> over a year now but in the last three weeks or so I'm seeing a ton of
> Stale NFS File Handle errors; especially in my overnight builds.
>
> Most of my clients are FC3 and a couple of Solaris boxes running a stock
> configuration. All we're doing is serving up NFS and compiling with
> GCC. We're seeing this error more and more and the harder I try to
> track it down, the more we're seeing it (ok, maybe that's my
> imagination).
>
> I'm guessing that the problem has to be somewhere in the FC3 server
> because I've still got some Solaris NFS servers that have been running
> for years with no problems.
>
> What should I be looking for in tracking this error down? Should I
> upgrade my kernel? Should I throw away FC3 and go to Enterprise Linux?
> I'm at the end of my rope here because this is now causing a major set
> back to our development team!
Kernels prior to 2.6.12 (if memory serves me correctly) had a series of
errors in the code that converts filehandles into valid dentries on the
server. Upgrading to the FC4 kernel, which I believe to be 2.6.14 based,
is therefore very likely to solve your problem.
Cheers,
Trond
next prev parent reply other threads:[~2006-02-03 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 18:05 Brian D. McGrew
2006-02-03 19:09 ` Trond Myklebust [this message]
2006-02-03 19:28 ` Roger Heflin
2006-02-03 19:24 ` Roger Heflin
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=1138993744.7861.18.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=brian@visionpro.com \
--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
all inboxes | Powered by JetHome®