No connection datastore NFS

[Protoburger]

Hi all,

I saw a lot of threads about this, but none of the work<span class="468313214-20022009">-around worked for me.

I'm using ESX 3.5 mounting a NFS ZFS Solaris.

When I log in into the ESX and run an ls I've got:

ls: reading directory /vmfs/volumes/VMFS-0003/: Input/output error

But accessing this Datastore through the VirtualCenter I can see the files there.

IN vmkernel.log I have:

NFS: 257: Mount: (VMFS-0003) Server (10.6.0.86) VMFS-0003<span class="468313214-20022009"> Volume: (/storage/VMFS-0003) not responding

Feb 20 10:55:10 vmkernel: 0:00:19:35.618 cpu1:1041)WARNING: NFS: 1736: Failed to get attributes (No connection) Feb 20 10:55:10 vmkernel: 0:00:19:35.618 cpu1:1041)FSS: 390: Failed with status No connection for b00f 36 9 9916d75c 24aa8d08 3000a 0 6 3000a 0 6 0 0 0 Feb 20 10:55:10 vmkernel: 0:00:19:35.618 cpu2:1039)WARNING: NFS: 1736: Failed to get attributes (No connection) Feb 20 10:55:10 vmkernel: 0:00:19:35.618 cpu2:1039)FSS: 390: Failed with status No connection for b00f 36 9 9916d75c 24aa8d08 3000a 0 6 3000a 0 6 0 0 0 Feb 20 10:55:12 vmkernel: 0:00:19:37.988 cpu2:1039)WARNING: NFS: 1736: Failed to get attributes (No connection) Feb 20 10:55:12 vmkernel: 0:00:19:37.988 cpu2:1039)FSS: 390: Failed with status No connection for b00f 36 9 9916d75c 24aa8d08 3000a 0 6 3000a 0 6 0 0 0 Feb 20 10:55:12 vmkernel: 0:00:19:37.988 cpu2:1039)WARNING: NFS: 1736: Failed to get attributes (No connection) Feb 20 10:55:12 vmkernel: 0:00:19:37.988 cpu2:1039)FSS: 390: Failed with status No connection for b00f 36 9 9916d75c 24aa8d08 3000a 0 6 3000a 0 6 0 0 0 Feb 20 10:55:<span class="468313214-20022009">13 vmkernel: 0:00:19:<span class="468313214-20022009">38.746 cpu0:<span class="468313214-20022009">1040)WARNING: NFS: 281: Mount: (VMFS-0003) Server (10.6.0.86) VMFS-0003 Volume: (/storage/VMFS-0003) OK

I have this mounted into two clusters.

One all the ESX works and the other only one is working, the other two are getting this error.

Thanks !!

</div>

[kjb007]

Can you run a vmkping from your ESX servers to the NFS server from the bad hosts? Has your IP changed, or are you exporting the share by IP or by subnet?

-KjB

[Lightbulb]

Please if you can clarify this stament:

"I have this mounted into two clusters. One all the ESX works and the other only one is working, the other two are getting this error."

You have two ESX clusters, yes?

On one ESX cluster (Cluster A) all NFS mounts are functional, yes?

On the other ESX cluster (Cluster B) only one mount is working ???

"<span class="468313214-20022009">the other two are getting this error" does this refer to the hosts in (Cluster B)??

Have you tried to vmkping to the NFS target address from all ESX hosts?

[Protoburger]

Sorry guys.... It was a networking problem...

The cluster that were able to mount it because its in the same switch... The other cluster is into an another switch and the network team made a maintanance into this uplink.,..

Thanks !!!