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.
Hi Ben, Thanks for the quick reply. I'm using windows 2008 r2, it's deploying to AWS so we're not tied to the OS version if there are issues. The NFS version is 3. The mount seems fine for access through file explorer and apps run from command line, I only see the failure when it's an IIS application.
-----Original Message-----
From: Ben Turner [mailto:bturner@xxxxxxxxxx]
Sent: Thursday, 12 March 2015 10:24 PM
To: Jarvis, Jeremy
Cc: gluster-users@xxxxxxxxxxx
Subject: Re: NFS gluster mount on Windows
Hi Jeremy. A couple things first, as of today gluster only supports NFS v3 so make sure you are using v3 and tcp mounts. I haven't personally tested Windows NFS with gluster, which version of Windows are you using? I would be happy to setup a test in our lab in hopes of helping get this working, I have seen issues with other OSs mounting gNFS that had to be resolved, maybe we are hitting something similar here.
-b
----- Original Message -----
> From: "Jeremy Jarvis" <jeremy.jarvis@xxxxxxxxxxxxxxxxxxxxx>
> To: gluster-users@xxxxxxxxxxx
> Sent: Thursday, March 12, 2015 3:57:00 AM
> Subject: NFS gluster mount on Windows
>
>
>
> Hi,
>
>
>
> I’m trying to use Windows Services for NFS to expose a gluster node
> and access this folder with an Application Pool Identity. I can map
> the drive correctly and read access works but I can’t get write working.
>
>
>
>
>
> The procedure I’m using is:
>
> Set the DefaultApplicationPoolIdentity to use user “CustomUser”
>
>
>
> Set the following environment variables to 0 (for root)
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS
> \CurrentVersion\Default\AnonymousUid
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS
> \CurrentVersion\Default\AnonymousGid
>
>
>
> Open a cmd with “CustomUser”
>
> mount -o nolock <ip-of-gluster>:/datapoint Z:
>
> SUCCESS
>
>
>
> Then the iis application is supposed to write log files out to Z:\ but
> always fails. I wrote a small test app that stats the folder and I can
> successfully stat the directory with “CustomUser”. Right click >
> Properties>NFS Attributes shows RWX for all and the NFS Mount Options
> shows UID 0 Primary GID 0.
>
>
>
> I can’t think of anything else that would be standing in the way. Any
> advice is greatly appreciated.
>
>
>
> Thanks, Jeremy.
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users@xxxxxxxxxxx
> http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
