From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: "martin.knoblauch " <"martin.knoblauch "@mscsoftware.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: nfs_statfs: statfs error = 116
Date: Thu, 13 Nov 2003 11:00:01 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0311131052260.31147@chaos> (raw)
In-Reply-To: <shssmks70gc.fsf@charged.uio.no>
On Thu, 13 Nov 2003, Trond Myklebust wrote:
> >>>>> " " == Richard B Johnson <root@chaos.analogic.com> writes:
>
> > ESTALE happens when a mounted file-system is on a server that
> > went down or re-booted. The file-handles are then "stale".
>
> Sort of. It means that the server is unable to find the file that
> corresponds to the filehandle that the client sent it. If the server
> strictly follows the NFS specs, then this is only supposed to happen
> if somebody else has deleted the file (and this is why designing a
> scheme for generating filehandles is such a difficult job).
>
> Some broken servers do, however, "lose" the file in other interesting
> and unpredictable ways.
>
> > 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.
>
> ERESTARTSYS actually just means that a signal was received while
> inside a system call. If this results in a interruption of that
> syscall, the kernel is supposed to translate ERESTARTSYS into the user
> error EINTR.
>
> Userland should therefore never have to handle ERESTARTSYS errors.
>
Hmmm, Maybe I'm getting confused by all the winning-lottery messages,
but it's in the syscall specifications for connect() and
even fcntl(). http:/www.infran.ru/Techinfo/syscalls/syscalls_43.html
Also, maybe Linux now claims exclusive ownership and keeps it internal,
but some networking software, nfsd and pcnfsd, might not know about that.
I've seen ERESTARTSYS returned from a DOS (actually FAT) file-handle use
after a server has crashed and come back on-line.
Moot point, though, the reported errors were internal via syslog, which
was not previously known when I responded.
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 15:58 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
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 [this message]
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.0311131052260.31147@chaos \
--to=root@chaos.analogic.com \
--cc="martin.knoblauch "@mscsoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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®