From: Jesse Pollard <jesse@cats-chateau.net>
To: Martin.Knoblauch@mscsoftware.com, root@chaos.analogic.com
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs_statfs: statfs error = 116
Date: Thu, 13 Nov 2003 14:26:25 -0600 [thread overview]
Message-ID: <03111314262500.15082@tabby> (raw)
In-Reply-To: <OF8497F0B5.C94E6443-ONC1256DDD.0051048E-C1256DDD.0051C1A9@mscsoftware.com>
On Thursday 13 November 2003 08:52, Martin.Knoblauch@mscsoftware.com wrote:
> "Richard B. Johnson" <root@chaos.analogic.com> wrote on 11/13/2003 03:39:53
>
> PM:
> > On Thu, 13 Nov 2003, martin.knoblauch wrote:
[snip]
> > ESTALE happens when a mounted file-system is on a server that
> > went down or re-booted. The file-handles are then "stale".
>
> I am "alomost" sure that there were no reboot or failover events at the
> time of most of the stale messages. But I'm not going to lay my hand on the
> book for that.
ESTALE should occur whenever the client looses connection to the server,
or thinks it has lost connection. It isn't directly related to the server
other than the fact that a server reboot will also cause it to happen.
This should be a transient failure that recovers when communication verified
from some of the timeouts/retries associated with NFS.
At worst, it can require a remount of the NFS volumn.
next prev parent reply other threads:[~2003-11-13 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 14:15 nfs_statfs: statfs error = 116 martin.knoblauch
2003-11-13 14:39 ` Richard B. Johnson
2003-11-13 14:52 ` Martin.Knoblauch
2003-11-13 20:26 ` Jesse Pollard [this message]
2003-11-13 20:34 ` Trond Myklebust
2003-11-14 8:43 ` Martin.Knoblauch
2003-11-14 13:49 ` Trond Myklebust
2003-11-14 14:22 ` Martin.Knoblauch
2003-11-13 15:27 ` Trond Myklebust
2003-11-13 16:00 ` Richard B. Johnson
2003-11-13 17:03 ` Trond Myklebust
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=03111314262500.15082@tabby \
--to=jesse@cats-chateau.net \
--cc=Martin.Knoblauch@mscsoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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