From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nfs is stupid ("getfh failed")
Date: Fri, 7 Sep 2001 02:59:47 +0100 [thread overview]
Message-ID: <20010907025947.E7329@kushida.degree2.com> (raw)
In-Reply-To: <002b01c136e1$3bb36a80$81d4870a@cartman>
In-Reply-To: <002b01c136e1$3bb36a80$81d4870a@cartman>; from rothwell@holly-springs.nc.us on Thu, Sep 06, 2001 at 10:35:53AM -0400
Michael Rothwell wrote:
> server# tail /var/log/messages
> Sep 6 09:37:43 gateway rpc.mountd: authenticated mount request from
> 192.168.1.133:933 for /export (/export)
> Sep 6 09:37:43 gateway rpc.mountd: getfh failed: Operation not permitted
I'm seeing this message quite often with one Linux 2.4.7 system
automounting another. As long as A has B's filesystem mounted, all is
ok. Then A times out, unmounts, and later wants to remount B's
filesystem. Then, sometimes, I see a message much like yours.
It doesn't seem to need a reboot to cause this problem, and the fix I
have found is to kill and restart the NFS server: /etc/init.d/nfs
restart.
I have no idea why it happens, or why restarting nfsd or mountd fixes it.
-- Jamie
next prev parent reply other threads:[~2001-09-07 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 14:35 nfs is stupid ("getfh failed") Michael Rothwell
2001-09-07 1:59 ` Jamie Lokier [this message]
2001-09-11 7:06 ` Neil Brown
2001-09-11 9:55 ` Jamie Lokier
2001-09-11 10:01 ` Neil Brown
2001-09-07 11:47 ` Neil Brown
2001-09-07 12:58 ` Michael Rothwell
2001-09-07 14:17 ` Tim Walberg
2001-09-08 0:02 ` Johan Kullstam
2001-09-08 13:38 ` Alan Cox
2001-09-09 10:05 ` Henning P. Schmiedehausen
2001-09-09 16:44 ` Michael Rothwell
2001-09-10 6:55 ` Neil Brown
2001-09-10 9:32 ` Marcus Sundberg
2001-09-11 7:07 ` Neil Brown
2001-09-12 10:44 ` Marcus Sundberg
2001-09-12 11:13 ` Trond Myklebust
2001-09-12 12:22 ` Neil Brown
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=20010907025947.E7329@kushida.degree2.com \
--to=lk@tantalophile.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.