From: James Pearson <james-p@moving-picture.com>
To: nfs@lists.sourceforge.net
Subject: rpc.mountd: getfh failed: Operation not permitted
Date: Fri, 23 Jan 2004 13:26:59 +0000 [thread overview]
Message-ID: <40112123.D2A8518D@moving-picture.com> (raw)
I have a strange problem with an NFS client that can not mount file
systems from some NFS servers.
e.g.:
mount clark:/disk1 /mnt/tmp
mount: clark:/disk1 failed, reason given by server: Permission denied
The server logs:
Jan 23 12:56:02 clark rpc.mountd: authenticated mount request from
rc0478:623 for /disk1 (/disk1)
Jan 23 12:56:02 clark rpc.mountd: getfh failed: Operation not permitted
However, doing:
mount clark:/disk2 /mnt/tmp
works fine - after this mount, /proc/mounts shows:
clark:/disk2 /mnt/tmp nfs
rw,v3,rsize=32768,wsize=32768,hard,udp,lock,addr=clark 0 0
On the server, /disk1 and /disk2 are separate disks exported in exactly
the same way:
/disk1 *(rw)
/disk2 *(rw)
The server is running a 2.4.19 based kernel with nfs-utils v0.3.3
(RedHat 7.2) (all a bit old, but they work fine)
The same client (running a 2.4.23 based kernel) is having the same
problem with a few other servers (but not all). Some of these other
servers are running a 2.4.21 based kernel.
However, every other client (100's of them) has no problems mounting
these same filesystems.
Any ideas?
Thanks
James Pearson
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-01-23 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 13:26 James Pearson [this message]
[not found] <20050203041550.746BD89D13@sc8-sf-spam1.sourceforge.net>
2005-02-03 17:52 ` rpc.mountd: getfh failed: Operation not permitted Jos van Wezel
2005-02-03 19:40 ` Steve Dickson
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 23:03 jehan.procaccia
2005-02-02 14:02 ` Steve Dickson
2003-08-06 15:08 Marc Schmitt
2003-08-19 14:50 ` Marc Schmitt
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=40112123.D2A8518D@moving-picture.com \
--to=james-p@moving-picture.com \
--cc=nfs@lists.sourceforge.net \
/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