I have the same trable as Richard Mace http://lists.freebsd.org/pipermail/freebsd-questions/2009-December/209334.html nfs server ]>uname -a FreeBSD bazar 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu Feb 25 14:42:08 MSK 2010 In rc.conf: nfs_server_enable="YES" #nfs_server_flags="-u -t -n 16" nfsv4_server_enable="YES" nfsuserd_enable="YES" mountd_flags="-r" rpcbind_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" nfs_client_enable="YES" in exports: /exp/home -maproot=0:0 192.168.3.195 10.144.142.57 V4: /exp /exp/fbsd71 /exp/ports /exp/distfiles /exp/fbsd_src/7.2/src /exp/fbsd_src/8.0/src /exp/fbsd_src/stable/src ]>showmount -e Exports list on localhost: /exp/ports Everyone /exp/home 192.168.3.195 10.144.142.57 10.144.142.54 /exp/fbsd_src/stable/src Everyone /exp/fbsd_src/8.0/src Everyone /exp/fbsd_src/7.2/src Everyone /exp/fbsd71 Everyone /exp/distfiles Everyone On client ]>uname -a FreeBSD skuns.gsm900.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Wed Jan 20 10:55:34 MSK 2010 in rc.conf: nfsuserd_enable="YES" nfscbd_enable="YES" nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" rpcbind_enable="YES" in fstab 10.144.140.160:/distfiles /exp/distfiles nfs rw,nfsv4,noauto 0 0 try to mount /exp/distfiles ]>mount /exp/distfiles ]> try to write ]>touch /exp/distfiles/t touch: /exp/distfiles/t: Permission denied ls and read files ok. p.s. showmount on server dosnt show clients when client has mounted share. -- alexs
On Sat, 27 Feb 2010, alexs@ulgsm.ru wrote:> > try to mount /exp/distfiles > ]>mount /exp/distfiles > ]> > > try to write > ]>touch /exp/distfiles/t > touch: /exp/distfiles/t: Permission denied > > > ls and read files ok. >When writes fail for me, it's usually a uid, gid vs user/group name mapping problem. Does "ls -lg" report correctuser and group names? (If you see "nobody", it is usually the "domain" for nfsuserd not being set to the same thing. It should default to the domain part of "hostname", but can be overridden by the "-domain xx.yy" flag for nfsuserd.) If the user and group names look ok for "ls -lg", then it might be a name<-># mapping issue. When using AUTH_SYS, the numbers are in the authentication header and the names are in the open/create and they need to match up. (Also, the NFSv4 client normally specifies a group to be set, so it must be a group that the user is allowed to set it to. ie. a group in the user's group list on the client.) Looking at the packets via wireshark will show where the server is reporting the error and might hint at the problem. Good luck with it, rick