NFS datastore not accessible after updating esx3.5U3 to Patch11

[RAMLOCK]

Hi All,

I was using esx3.5U3 and my datastores were present on NetApp's NFS volume.I have updated my esx3.5U3 with Patch11. After that all my nfs datastores are not accessible.

Even if i try to create a new volume with nfs esxport i can access those in esx server. While accessing from VC server it is giving "NFS Error : Unable to query remote mount point's attributes"

My VC server is 2..5. Are the new patch compatible with the NFS version?

[christianZ]

I would try to remove and then recreate the vmkernel port - can you "vmkping" your nas?

[RAMLOCK]

Tried following steps and it is working now.

1. rpcinfo -u 10.72.248.225 nfs 3

rpcinfo: RPC: Port mapper failure - RPC: Unable to receive program 100003 version 3 is not available

1. service portmap start

Starting portmapper:

1. service nfs start Starting

NFS services:

Starting NFS daemon:

Starting NFS mountd:

1. rpcinfo -u 10.72.248.225 nfs 3

program 100003 version 3 ready and waiting

But i have to create a new nfs datastore. Old one is not accessible. ESX leaves footprints behind in case of any error encounter with datastore or vm. The same name can not be used.

Or we need to restart the ESX server. As ESX server is being shared by many people so restarting option is not applicable always. Is there a set of command to do the clean up without

restarting the system.

[kooltechies]

Hi,

Are you saying that you are able to access the nfs on the ESX command line but not through VC ? If this is right then the NFS mounts are ok. Try the steps mentioned below.

1) Directly connect your ESX server to VI client and not VC see if you are able to see the NFS datastore.

2) Check if your VI client and VC server has the same version ( You can check that in help tab of VI client connected to VC) , if there is a difference you can download a new VI client from ESX.

3) Check in VC vpxa logs and hostd.log

Thanks,

Samir

P.S : If you think that the answer is helpful please consider rewarding points.

[kooltechies]

Old NFS datastore is there or not ? If it is there then the caching may be done in VC , you can check that from the datastore browser view in VI client.

Thanks,

Samir

P.S : If you think that the answer is helpful please consider rewarding points.

[RAMLOCK]

I tried from esx server VI client also. The error message in both the cases VC as well as esx vi "Can not open volume: /vmfs/volumes/eboe5fc1-9f21ecfb

But when i check from esx server i could not find above mentioned id :

volumes]# ls -la

total 3080

drwxr-xr-x 1 root root 512 Mar 14 21:00 .

drwxrwxrwt 1 root root 512 Mar 10 02:11 ..

drwxr-xr-t 1 root root 980 Dec 17 22:25 49492eeb-1e23da91-6029-001a64c6f54e

drwxr-xr-t 1 root root 1260 Mar 10 02:41 499d8667-c368c790-a6f2-001a64c6f54e

drwxr-xr-t 1 root root 1120 Mar 3 00:17 49ac297d-0b5a989d-58f3-001a64c6f54e

drwxr-xr-x 1 root root 4096 Mar 14 14:02 589959cd-a0dd07c0

drwxr-xr-x 1 root root 4096 Mar 14 13:19 c62c599e-09aac8fe

lrwxr-xr-x 1 root root 17 Mar 14 21:00 deduped_nfs_ds -> c62c599e-09aac8fe

lrwxr-xr-x 1 root root 35 Mar 14 21:00 FCP248-40 -> 49ac297d-0b5a989d-58f3-001a64c6f54e

lrwxr-xr-x 1 root root 35 Mar 14 21:00 smvi-248-225:storage1 -> 49492eeb-1e23da91-6029-001a64c6f54e

lrwxr-xr-x 1 root root 35 Mar 14 21:00 vf_iscsi_sw_ds1 -> 499d8667-c368c790-a6f2-001a64c6f54e

lrwxr-xr-x 1 root root 17 Mar 14 21:00 vf_nfs_ds -> 589959cd-a0dd07c0

volumes]# pwd

/vmfs/volumes