From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "martin.knoblauch " <"martin.knoblauch "@mscsoftware.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs_statfs: statfs error = 116
Date: Thu, 13 Nov 2003 09:39:53 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0311130927280.30784@chaos> (raw)
In-Reply-To: <3FB391FC.2090406@mscsoftware.com>
On Thu, 13 Nov 2003, martin.knoblauch wrote:
> Hi,
>
> sorry if OT, but what is above message trying to tell me? Where can I
> find a translation of the numbers? We are seeing 116 very frequently,
> 512 and 5 on occasion.
>
ESTALE is "errno" 116
EIO is "errno" 5
ERESTARTSYS is "errno" 512
You can find these in /usr/include/asm/errno.h (not good to
directly include in a program).
The program reporting these errors should have included:
<errno.h>
<string.h>
Then used...
strerror(errno);
or
perror("");
etc.
Errno 512 should never be seen by user-mode program, so the
header file, /usr/include/linux/errno.h, states...
ESTALE happens when a mounted file-system is on a server that
went down or re-booted. The file-handles are then "stale".
EIO is a general catch-all for an I/O error.
ERESTARTSYS is the error returned by a server that has
re-booted that is supposed to tell the client-side software
to get a new file-handle because of an attempt to access with
a stale file-handle. When getting this error, the client
should have reopened the file(s) to obtain a new handle.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-11-13 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 14:15 martin.knoblauch
2003-11-13 14:39 ` Richard B. Johnson [this message]
2003-11-13 14:52 ` Martin.Knoblauch
2003-11-13 20:26 ` Jesse Pollard
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=Pine.LNX.4.53.0311130927280.30784@chaos \
--to=root@chaos.analogic.com \
--cc="martin.knoblauch "@mscsoftware.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®