It really depends on how Windows is assigning a UNIX uid during NFS access. Gluster just takes the Unix UID encoded in the auth header as-is. In this case that number is actually the unsigned representation of -2. Regarding performance, please look for any odd messages in the NFS server logs. Avati On Tue, Jul 30, 2013 at 3:21 AM, Nux! <nux at li.nux.ro> wrote: > On 30.07.2013 11:03, Anand Avati wrote: > >> What unix uid is the windows client mapping the access to? I guess the >> permission issue boils down to that. You can create a file under the mode >> 777 dir, and check the uid/gid from a linux client. Then make sure the >> dirs >> you create can be writeable by that uid/gid. >> > > Yep, it's some weird UID: > drwxr-xr-x 2 4294967294 4294967294 10 Jul 30 11:14 New folder > > So the solution would be to "chown 4294967294:4294967294 directory"? Was > hoping for something more elegant, but it'll have to do I guess. > > Also, another problem I notice is that doing anything on this NFS mount in > windows is extremely slow and I frequently get a "Not Responding" Explorer > window. Any thoughts on why this might happen? > > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130730/bc00551d/attachment.html>
