Date: Mon, 1 Mar 2010 17:32:31 -0500 (EST) From: Rick Macklem <rmacklem@uoguelph.ca> To: alexs@ulgsm.ru Cc: FreeBSD-stable@freebsd.org Subject: Re: Cannot write to nfsv4 share Message-ID: <Pine.GSO.4.63.1003011725230.28488@muncher.cs.uoguelph.ca> In-Reply-To: <20100227082359.GA11868@mail.ulgsm.ru> References: <20100227082359.GA11868@mail.ulgsm.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.1003011725230.28488>