From: "Michael Rothwell" <rothwell@holly-springs.nc.us>
To: <linux-kernel@vger.kernel.org>
Subject: nfs is stupid ("getfh failed")
Date: Thu, 6 Sep 2001 10:35:53 -0400 [thread overview]
Message-ID: <002b01c136e1$3bb36a80$81d4870a@cartman> (raw)
Two systems that worked fine for weeks, both running 2.4.[7,8] kernels. The
server is running 2.4.8 and exporting a reiserfs filesystem via nfs. Or it
was, anyway. The server was shut down and brought back up (power failure).
The client was then
rebooted.
server# cat /etc/exports
/export 192.168.1.*(rw,no_root_squash)
/export/home 192.168.1.*(rw,no_root_squash)
client# mount /export
mount: 192.168.1.1:/export failed, reason given by server: Permission denied
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
... so, rebooting two working systems seems to kill NFS. Any ideas why?
On a related topic, will Linux ever have a better file-service protocol?
next reply other threads:[~2001-09-06 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 14:35 Michael Rothwell [this message]
2001-09-07 1:59 ` nfs is stupid ("getfh failed") Jamie Lokier
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='002b01c136e1$3bb36a80$81d4870a@cartman' \
--to=rothwell@holly-springs.nc.us \
--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