public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lehrer <mark@tpsit.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Mark Lehrer <mark@tpsit.com>, linux-nfs@vger.kernel.org
Subject: Re: Time to declare war on "stale nfs file handle"
Date: Thu, 21 Feb 2013 14:01:50 -0700 (MST)	[thread overview]
Message-ID: <alpine.DEB.1.00.1302211400050.801@shell> (raw)
In-Reply-To: <20130220202114.GA4995@fieldses.org>


>> been running for awhile and then I fail over, clients get the dreaded
>> Stale NFS file handle error on any open files.  In this case they are
>
> That's weird.  The contents of /proc/net/rpc/nfsd.fh/content and
> /proc/net/rpc/nfsd.export/content on both nodes after a failed failover
> might be interesting.

Cool, this is exactly the kind of information I was looking for.


> What filesystem are you exporting?

ext4.

Thanks!
Mark


      reply	other threads:[~2013-02-21 21:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 22:36 Time to declare war on "stale nfs file handle" Mark Lehrer
2013-02-20 20:21 ` J. Bruce Fields
2013-02-21 21:01   ` Mark Lehrer [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=alpine.DEB.1.00.1302211400050.801@shell \
    --to=mark@tpsit.com \
    --cc=bfields@fieldses.org \
    --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