Jeff,
Thanks for the response. I did see that thread previously, with the only difference being
that the file isn't getting written out. Let me give that fix a try and see what
happens.
Steve
--
Stephen Jones
Group Lead / Principal Software Engineer
The MITRE Corporation
Phone: (781)271-2517 Email: srjones(a)mitre.org
On 10/15/18, 8:17 AM, "Jeff Layton" <jlayton(a)redhat.com> wrote:
On Thu, 2018-10-11 at 13:46 +0000, Jones, Stephen R. wrote:
Hello all;
I’m running into an interesting problem, and since I haven’t seen anything similar on the
mailing or issues list I thought I would see if there’s something I’m missing. Here’s my
setup:
CentOS 7 server running GlusterFS 4.1.4 and NFS-Ganesha 2.6.3
Windows 10 Pro system with nfs-client installed. Mounting the external NFS drive on the
system (v3), and have made uid and guid changes in the registry to match the uid for the
share.
With this setup, I’m able to copy most files from the windows system to the share without
a problem. However, if the file on windows has the ‘Read-Only’ attribute set, the copy
fails with a permission denied error, and looking at the Wireshark trace I’m seeing an
NFS3ERR_ACCES error. Is there something I can set in the NFS-Ganesha config file to
resolve this issue?
Thanks,
Steve
Sounds like the same problem we recently had with ceph:
https://github.com/nfs-ganesha/nfs-ganesha/issues/349
If you see the NFSERR3_ACCESS happening on the COMMIT call, then gluster
may need a similar solution.
--
Jeff Layton <jlayton(a)redhat.com>