From: Jose Santiago <jsantiago@chrysalisdev.com>
To: nfs@lists.sourceforge.net
Subject: getfh failed: Operation not permitted
Date: Mon, 12 Aug 2002 18:30:00 -0500 [thread overview]
Message-ID: <3D5844F8.5080708@chrysalisdev.com> (raw)
Server Name: bfs1
Client Name: rtr01
I am having problems mounting bfs1:/data on NFS client rtr01 . The
server log says:
Aug 12 14:15:27 bfs1 rpc.kmountd: getfh failed: Operation not permitted
when I attempt the mount.
The client can mount bfs1:/ bfs1:/data/backup and all of the other mount
points and subdirectories under the mount points except for bfs1:/data
and other subdirectories under it. Other NFS clients can mount
bfs1:/data and all mount points just fine.
A pointer in the right direction would be much appreciated.
Both client and Server:
Kernel version 2.4.19pre1
nfs-utils version 0.3.3
mount version 2.11n
Server /etc/exports:
/ \
bfs1.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
inet1.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
wsa147.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
127.0.0.0/255.0.0.0(no_root_squash,rw,insecure,nohide) \
10.0.0.0/255.0.0.0(rw,insecure,nohide)
/data \
bfs1.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
inet1.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
wsa147.chrysalisdev.com(no_root_squash,rw,insecure,nohide) \
127.0.0.0/255.0.0.0(no_root_squash,rw,insecure,nohide) \
10.0.0.0/255.0.0.0(rw,insecure,nohide)
/data/backup \
127.0.0.0/255.0.0.0(no_root_squash,rw,insecure,nohide) \
10.0.0.0/255.0.0.0(no_root_squash,rw,insecure,nohide) \
172.16.0.0/255.240.0.0(no_root_squash,rw,insecure,nohide) \
192.168.0.0/255.255.0.0(no_root_squash,rw,insecure,nohide)
/cdrom \
*(ro,insecure,nohide)
/floppy *(rw,insecure,nohide)
Server exportfs -v:
/data bfs1.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/data inet1.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/data
wsa147.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/ bfs1.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/ inet1.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/ wsa147.chrysalisdev.com(rw,async,wdelay,nohide,insecure,no_root_squash)
/data/backup
127.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/data/backup
10.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/data/backup
172.16.0.0/255.240.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/data/backup
192.168.0.0/255.255.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/data 127.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/data 10.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,root_squash)
/ 127.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,no_root_squash)
/ 10.0.0.0/255.0.0.0(rw,async,wdelay,nohide,insecure,root_squash)
/floppy <world>(rw,async,wdelay,nohide,insecure,root_squash)
/cdrom <world>(ro,async,wdelay,nohide,insecure,root_squash)
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-08-12 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 23:30 Jose Santiago [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-12 19:45 getfh failed: Operation not permitted Jose Santiago
[not found] ` <20020813133428.GA2393@farm.ecs.umass.edu>
2002-08-13 14:26 ` Jose Santiago
2002-08-12 19:31 Jose Santiago
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=3D5844F8.5080708@chrysalisdev.com \
--to=jsantiago@chrysalisdev.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