Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

Unable to mount NFS datastore to 2 out of 3 hosts

$
0
0

Hello All,

 

I'm new so please bear with me....

 

Our infrastructure contains 3 main hosts, we use a Netapp SAN to connect our NFS datastores to, for some reason even when I manually try connecting the datastore to hosts i'm unable to do it on 2 of the 3.

 

All 3 hosts are on the same network segment, they have a vmkernel interface that connects to the VLAN of our SAN (so all traffic flows correctly, and there is another VMK interface dedicated for management as well) I can connect a datastore from 1 host to all 3 of our SAN controllers, but for some reason the 1 SAN controller thats at our DR site I can't connect to (again on 2 of the 3 hosts)

 

I went through the VMKERNEL.LOG and noticed this showing up

 

 

2013-02-01T16:23:58.453Z cpu14:5066)NFS: 157: Command: (mount) Server: (X.X.X.51) IP: (X.X.X.51) Path: (/vol/pdvideo) Label: (Surveillance_Video) Options: (None)
2013-02-01T16:23:58.457Z cpu19:5066)NFS: 292: Restored connection to the server X.X.X.51 mount point /vol/pdvideo, mounted as b2e55d25-84689502-0000-000000000000 ("Surveillance_Video")
2013-02-01T16:23:58.457Z cpu19:5066)NFS: 217: NFS mount X.X.X.51:/vol/pdvideo status: Success
2013-02-01T16:24:09.468Z cpu7:4103)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:09.470Z cpu7:4103)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:09.472Z cpu7:4103)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:39.475Z cpu6:4102)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:39.476Z cpu6:4102)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:39.477Z cpu6:4102)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:24:43.097Z cpu18:474641)NFS: 157: Command: (mount) Server: (X.X.X.51) IP: (X.X.X.51) Path: (/vol/pdvideo) Label: (Surveillance_Video) Options: (None)
2013-02-01T16:24:43.101Z cpu18:474641)NFS: 292: Restored connection to the server X.X.X.51 mount point /vol/pdvideo, mounted as b2e55d25-84689502-0000-000000000000 ("Surveillance_Video")
2013-02-01T16:24:43.101Z cpu18:474641)NFS: 217: NFS mount X.X.X.51:/vol/pdvideo status: Success
2013-02-01T16:25:09.480Z cpu8:4104)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:25:09.481Z cpu8:4104)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:25:09.482Z cpu8:4104)WARNING: NFS: 217: Got error 13 from mount call
2013-02-01T16:25:39.484Z cpu8:4104)WARNING: NFS: 217: Got error 13 from mount call

 

 

NFS: 190: NFS mount X.X.X.51:/vol/pdvideo failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.

 

In this example you will see that it shows a status of Success but then I get all these Error 13's.

 

I verified all the permissions were set correctly on the /vol and made sure from both the SAN controller and the host that both can communicate with each other. I did a health check through the netapp snapin for vcenter and all show healthy. It pings the SAN and checks connectivity to all datastores, which we have other datastores pointing to this SAN controller as well as the effected host. So it makes no sense why I can't add a new datastore to this host.

 

I'm a newb so be kind... please haha

 

Thanks for your help!


Viewing all articles
Browse latest Browse all 179681

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>