Unable to write to NFS datastore in Vcenter
Hello all,
I am having an issue with an NFS datastore within Vcenter. I have a NFS share on a Win2k3 server which I am able to successfully mount. However.. I cannot write to it even though the permissions seem correct. This server is hooked up to an EVA Storage vault drive array with 2TB of storage.
It looks like it's not listing the contents either as when I try to mount it, it shows as 0.00B capacity.. and I know there are files in that NFS datastore. From this same host, I can mount other NFS datastores successfully.
Please help.. been at this for 2 days banging my head on my desk! :(
Esxi-nfs-permissions.jpg
NFS-Permissions.jpg
NFS-Storage.jpg
I am having an issue with an NFS datastore within Vcenter. I have a NFS share on a Win2k3 server which I am able to successfully mount. However.. I cannot write to it even though the permissions seem correct. This server is hooked up to an EVA Storage vault drive array with 2TB of storage.
It looks like it's not listing the contents either as when I try to mount it, it shows as 0.00B capacity.. and I know there are files in that NFS datastore. From this same host, I can mount other NFS datastores successfully.
Please help.. been at this for 2 days banging my head on my desk! :(
Esxi-nfs-permissions.jpg
NFS-Permissions.jpg
NFS-Storage.jpg
gheist
By default ESXi alows to mount 8 NFS volumes.
ASKER
Thanks for your reply gheist, but I have no idea what that has to do with what I'm asking..
Mounting the NFS volume is not the issue here.. permissions seem to be, and I'm not sure where it's going wrong.
Mounting the NFS volume is not the issue here.. permissions seem to be, and I'm not sure where it's going wrong.
Windows has security log 3 clicks away to log all permission problems.
Size 0 on unix means that you could not connect nfsd, only mountd, if that helps..
Size 0 on unix means that you could not connect nfsd, only mountd, if that helps..
ASKER
It sort of makes sense since that's the problem I'm seeing but I don't know how to resolve this with server 2k3. Can you elaborate a bit more? I'm a bit new with Unix and NFS. With server 2008, I did not have these issues with permissions.
In 2008 firewall is per-program, in 2003 per-port
so make sure all these are open:
http://support.microsoft.com/kb/891760
so make sure all these are open:
http://support.microsoft.com/kb/891760
ASKER
There is no firewall active on the server. I have the service completely disabled. I am more curious about the Unix NFS stuff as that seems to be the real issue here.
You run windows and vmware, no idea where you halucinate about unix,
And "disable firewall" does not work in windows server. once you open control panel of firewall it comes back.
And "disable firewall" does not work in windows server. once you open control panel of firewall it comes back.
ASKER
The windows firewall is not running. The ICS service is completely disabled. It will not even open up in control panel. You can telnet to this box on all necessary ports. So the firewall would not be the issue here.
You said "Size 0 on unix means that you could not connect nfsd" That is what I believe the problem is, and I do not know what the fix is on Win2k3. My server 2008 datastores do not have this problem because I can use No Server Authentication with Unmapped user access on NFS shares.
Screenshot attached.
unmappeduseraccess.jpg
You said "Size 0 on unix means that you could not connect nfsd" That is what I believe the problem is, and I do not know what the fix is on Win2k3. My server 2008 datastores do not have this problem because I can use No Server Authentication with Unmapped user access on NFS shares.
Screenshot attached.
unmappeduseraccess.jpg
And what are the access permissions over network, for root user as vmware uses?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually vmware uses only root to access nfs, so it should not matter if you use anonymous mapping or root remapping to nobody or so. It will keep working as long as it can create file...
ASKER
Resolved after much frustration.