From: Nick Patavalis <npat@efault.net>
To: linux-nfs@vger.kernel.org
Subject: Re: 2.6.32, NFSv4, "Stale NFS file handle" problem
Date: Mon, 21 Feb 2011 11:30:18 +0200 [thread overview]
Message-ID: <AANLkTikyuyc0K2qXZf9ce5Y0ApMCsjsysEfg==gAxJJV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinZ61OZObYMeuisJ-H2+o3PgFM1K+kExyUMaTNL@mail.gmail.com>
Hi,
On Mon, Feb 21, 2011 at 11:09 AM, Nick Patavalis <npat@efault.net> wrote:
>
> On Mon, Feb 21, 2011 at 2:54 AM, Nick Patavalis <npat@efault.net> wrote:
>>
>> I don't know if this is an NFS bug, but seems a lot like it... My
>> server-host exports a few NTFS filesystems (read-only exports) using
>> NFSv4. Two client-hosts mount these file-systems.
>>
>> Client A runs 2.6.31, and client B 2.6.32. Client A works fine. Client
>> B, while it initially mounts everything ok, and for some time
>> everything works ok (or so it seems), after a while it starts
>> returning "Stale NFS file hande" errors for random files and
>> directories. Client A NEVER returns stale errors, EVEN after a server
>> reboot.
>>
>
> Some additional information.
>
> After the problem appears (i.e. after "client B" starts returning
> "stale file handle" errors), an "ls" on a file (directory) for
> which the file-handle is stale, with "sunrpc.nfs_debug = 1023"
> shows:
>
I also tried:
- Exporting /mnt (the NFSv4 preudo-root) without the "crossmount"
option (and having the clients mount the subordinate file-systems)
- Exporting /mnt with "crossmount" and having the client B (the
"problematic" one, running kernel 2.6.32) mount "server:/" instead
of the subordinate filesystems.
- Making client B mount with options: "ro,soft,proto=tcp"
(i.e. without the "nocto,actimeo=300")
No observable change in behavior. Client A (the one with kernel
2.6.31) works perfectly. Client B (the one with kernel 2.6.32) mounts
ok but, at some point in time, it starts returning "stale file handle"
errors (as described in the previous message).
At this point I start to run out of things to try! Any suggestions
would be greately appreciated.
Thanks again
/npat
prev parent reply other threads:[~2011-02-21 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 0:54 2.6.32, NFSv4, "Stale NFS file handle" problem Nick Patavalis
2011-02-21 9:09 ` Nick Patavalis
2011-02-21 9:30 ` Nick Patavalis [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='AANLkTikyuyc0K2qXZf9ce5Y0ApMCsjsysEfg==gAxJJV@mail.gmail.com' \
--to=npat@efault.net \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).