Shawn Webb wrote:
I have one OpenSolaris b134 server and one OpenSolaris b134 client. I'm trying
to mount an NFSv4 share from the client to the server.
How do you know it is NFSv4?
I.e., are you specifying this in either your maps or /etc/default/nfs?
The client's hostname is shawn-desktop and the server's is sully. Currently,
the NFS default domain is set to 0xfeedface.org.
Here's the command outputs:
sh...@shawn-desktop:~$ ls /net/192.168.2.6/tank/shares/shawn
ls: cannot open directory /net/192.168.2.6/tank/shares/shawn: Permission denied
You should get some snoop from this transaction.
r...@sully:~# sharemgr show -vp
default nfs=()
zfs
zfs/tank/ISOs nfs=() nfs:sys=(rw="*")
/tank/ISOs
zfs/tank/shares/edward smb=()
edward=/tank/shares/edward
zfs/tank/shares/mario smb=()
mario=/tank/shares/mario
zfs/tank/shares/shawn nfs=() smb=() nfs:sys=(rw="*")
shawn=/tank/shares/shawn
r...@sully:~# /bin/ls -vd /tank/shares/shawn
d---------+ 13 root root 19 Apr 18 20:45 /tank/shares/shawn
0:user:shawn:list_directory/read_data/add_file/write_data
/add_subdirectory/append_data/read_xattr/write_xattr/execute
/delete_child/read_attributes/write_attributes/delete/read_acl
/write_acl/write_owner/synchronize:file_inherit/dir_inherit:allow
What stands out to me is that the owner of the directory is root and not
shawn. And you are getting
EPERM back. I.e., it isn't the mount which is failing, it is the ls.
You can confirm that in two ways:
sh...@shawn-desktop:~$ mount | grep 192.168.2.6
or
sh...@shawn-desktop:~$ mount -o vers=3 192.168.2.6:/tank/shares/shawn /mnt
With the v3 mount, try an 'ls /mnt' and see whether you get EPERM or not.
You should check to see that the NFSv4 idmap domain is the same for both
machines:
cat /var/run/nfs4_domain
If it isn't, then you can set it in //etc/default/nfs.
/
If they are not the same, then your client request will be mapped to
"nobody" and not
"shawn". And that does not match your ACLs.
_______________________________________________
nfs-discuss mailing list
[email protected]
