I think I’m seeing a separate issue. I can set up the mount fine but using an IIS application it seems to always fail, read and write.
I’m debugging now to make sure I’m impersonating the correct user. From: Ryan Nix [mailto:ryan.nix@xxxxxxxxx]
Since I had a similar post earlier, this is what I found to work:
On your Gluster system:
gluster volume set volumename storage.owner-gid 0 (0 on CentOS is the ID for root)
gluster volume set volumename nfs.volume-access read-write
gluster volume set volumename nfs.rpc-auth-allow x.x.x.x
On your Windows system:
Install NFS services for Windows
Start Registry Editor
Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS \CurrentVersion\Default
Create two DWORD values named AnonymousUid and AnonymousGid
Set these values to the UID and GID of the Unix user you would like this NFS client to masquerade as. i.e. root's Unix ID on CentOS 7 is 0
Run cmd
mount -o anon x.x.x.x:/volumename G:
After doing the steps listed above, I can read and write to the Gluster volume from a Windows system over NFS. The only strange thing I can't figure out is why Windows still shows
a line through the mount point when a) its mounted and b) can be read and written to. On Thu, Mar 12, 2015 at 8:13 PM, Jarvis, Jeremy <jeremy.jarvis@xxxxxxxxxxxxxxxxxxxxx> wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users