52 TB NFS mount at Vsphere 5.5 Issue

[ganesh24pal]

Hi Team,

We have to mount 52 TB NFS at our Vsphere Server 5.5, but i am getting issue , Please find details of my scenirio.

NFS Server :- NAS Server Windows 2k8 R2 (Dell Server)

Vsphere 5.5

Note:- We able to telnet NFS Server

--------------------------------------------------------------------------

I am unable to Add NFS Server in my Vsphere 5.5

[a_p_]

Please provide some details of what you did so far, and any warnings/error messages you get.

How did you configure the NFS share and permissions in the Windows host?

How are you trying to mount the NFS share on the ESXi host?

Maybe some screenshots will help.

André

[ganesh24pal]

How did you configure the NFS share and permissions in the Windows host?

Ans:- Provided Read and Write Permission, and also given root level permission.

How are you trying to mount the NFS share on the ESXi host?

Ans:- Configuration>>Storage>>Add Data store>>Select "Network File System Option" and shared required details.

Maybe some screenshots will help.

Please find error.

[rcporto]

Check if this KB article helps: Cannot connect to NFS network share (1007352)

[ganesh24pal]

Dear Porto,

No goodluck for me .I am getting below error.

From same network we able to telnet the nas server.

============================

# cat /var/log/vmkernel.log | grep -i nfs

2014-06-02T18:20:33.581Z cpu6:33816)NFS: 157: Command: (mount) Server: (192.168.143.168) IP: (192.168.143.168) Path: (/newshare) Label: (datastore2) Options: (None)

2014-06-02T18:21:04.587Z cpu6:33816)NFS: 168: NFS mount 192.168.143.168:/newshare failed: Unable to connect to NFS server.

2014-06-02T18:36:31.248Z cpu1:33818)NFS: 157: Command: (mount) Server: (192.168.143.168) IP: (192.168.143.168) Path: (/newshare) Label: (datastore-002) Options: (None)

2014-06-02T18:37:02.185Z cpu0:33818)NFS: 168: NFS mount 192.168.143.168:/newshare failed: Unable to connect to NFS server.

2014-06-04T18:42:06.894Z cpu5:33819)NFS: 157: Command: (mount) Server: (192.168.143.168) IP: (192.168.143.168) Path: (/cctv/) Label: (datastore-007) Options: (None)

2014-06-04T18:42:37.238Z cpu2:33819)NFS: 168: NFS mount 192.168.143.168:/cctv/ failed: Unable to connect to NFS server.

~ #=========================================================================================

2014-06-04T18:55:00.383Z cpu5:32925)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x12 (0x412e80860200, 0) to dev "naa.600508e000000000c7485d73c5210d0c" on path "vmhba1:C1:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x0 0x0. Act:NONE

2014-06-04T18:57:14.651Z cpu3:32779)LinNet: map_skb_to_pkt:511: This message has repeated 645120 times: invalid vlan tag: 4095 dropped

2014-06-04T19:00:00.383Z cpu2:32791)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808801c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-06-04T19:00:00.383Z cpu2:32791)ScsiDeviceIO: 2337: Cmd(0x412e808801c0) 0x1a, CmdSN 0x373f from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-06-04T19:00:00.383Z cpu4:33206)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x12 (0x412e808801c0, 0) to dev "naa.600508e000000000c7485d73c5210d0c" on path "vmhba1:C1:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x0 0x0. Act:NONE

2014-06-04T19:01:56.548Z cpu6:38933)NFS: 157: Command: (mount) Server: (192.168.143.168) IP: (192.168.143.168) Path: (/newshare/VSOM-DATASTORE001) Label: (VSOM-DATASTORE001) Options: (None)

2014-06-04T19:01:56.548Z cpu6:38933)StorageApdHandler: 698: APD Handle 498e31cf-38313433 Created with lock[StorageApd0x4110c2]

2014-06-04T19:02:27.306Z cpu6:38933)StorageApdHandler: 745: Freeing APD Handle [498e31cf-38313433]

2014-06-04T19:02:27.306Z cpu6:38933)StorageApdHandler: 808: APD Handle freed!

2014-06-04T19:02:27.306Z cpu6:38933)NFS: 168: NFS mount 192.168.143.168:/newshare/VSOM-DATASTORE001 failed: Unable to connect to NFS server.

[ganesh24pal]

===========================================================================================================================

2014-06-04T19:13:59.681Z cpu2:35030)NFS: 157: Command: (mount) Server: (192.168.143.168) IP: (192.168.143.168) Path: (/newshare/VSOM-DATASTORE001) Label: (VSOM-DATASTORE011) Options: (None)

2014-06-04T19:13:59.681Z cpu2:35030)StorageApdHandler: 698: APD Handle 498e31cf-38313433 Created with lock[StorageApd0x4110c2]

2014-06-04T19:14:30.586Z cpu2:35030)StorageApdHandler: 745: Freeing APD Handle [498e31cf-38313433]

2014-06-04T19:14:30.586Z cpu2:35030)StorageApdHandler: 808: APD Handle freed!

2014-06-04T19:14:30.586Z cpu2:35030)NFS: 168: NFS mount 192.168.143.168:/newshare/VSOM-DATASTORE001 failed: Unable to connect to NFS server.

2014-06-04T19:15:00.383Z cpu6:32795)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e807f48c0, 0) to dev "mpx.vmhba32:C0:T0:L0" on path "vmhba32:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-06-04T19:15:00.383Z cpu6:32795)ScsiDeviceIO: 2337: Cmd(0x412e807f48c0) 0x1a, CmdSN 0x376e from world 0 to dev "mpx.vmhba32:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

=========================================================================

[ganesh24pal]

Hi Team,

is it there any issue with NFS bug issue .

Please suggest any bug fix or patches for Vsphere 5.5 . I unbale to take from below kb.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=207639...

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=207736...

2014-06-13T22:02:48.445Z: No correlator for vob.vmfs.nfs.server.disconnect

2014-06-13T22:02:48.445Z: [vmfsCorrelator] 31829077665us: [esx.problem.vmfs.nfs.server.disconnect] 192.168.143.172 /NFS 44e330db-a79984fb-0000-000000000000 datastorenfs

2014-06-13T22:03:21.351Z: [APDCorrelator] 31861983204us: [vob.storage.apd.timeout] Device or filesystem with identifier [44e330db-a79984fb] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.

2014-06-13T22:03:21.351Z: [APDCorrelator] 31861983678us: [esx.problem.storage.apd.timeout] Device or filesystem with identifier [44e330db-a79984fb] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I/Os will now be fast failed.

2014-06-13T22:04:07.457Z: [APDCorrelator] 31908088846us: [vob.storage.apd.exit] Device or filesystem with identifier [44e330db-a79984fb] has exited the All Paths Down state.

2014-06-13T22:04:07.457Z: No correlator for vob.vmfs.nfs.server.restored

2014-06-13T22:04:07.457Z: [vmfsCorrelator] 31908089269us: [esx.problem.vmfs.nfs.server.restored] 192.168.143.172 /NFS 44e330db-a79984fb-0000-000000000000 datastorenfs

2014-06-13T22:04:07.457Z: [APDCorrelator] 31908089322us: [esx.clear.storage.apd.exit] Device or filesystem with identifier [44e330db-a79984fb] has exited the All Paths Down state.

Message was edited by: ganesh24pal

[ganesh24pal]

Hi Friends,

========================================

Myself update Vmware patch from command line. Now facing below issue.

OLD Vmware ESXi Version 5.5.0 Build 13318120

After Vmware ESXi Version 5.5.0 Build 1881737

Patch File Name :- ESXi550-201406001

###########Error###############

2014-06-14T14:38:52.437Z cpu0:32768)VisorFSTar: 1960: block_cc.v00 for 0x135a0 bytes

2014-06-14T14:38:57.165Z cpu1:33261)Loading module vmkapi_socket ...

2014-06-14T14:38:57.166Z cpu1:33261)Elf: 1861: module vmkapi_socket has license VMware

2014-06-14T14:38:57.166Z cpu1:33261)Mod: 4780: Initialization of vmkapi_socket succeeded with module ID 7.

2014-06-14T14:38:57.166Z cpu1:33261)vmkapi_socket loaded successfully.

2014-06-14T14:39:18.918Z cpu0:33176)StorageApdHandler: 698: APD Handle  Created with lock[StorageApd0x410891]

2014-06-14T14:39:19.045Z cpu0:33176)StorageApdHandler: 698: APD Handle  Created with lock[StorageApd0x410891]

2014-06-14T14:39:23.119Z cpu3:33176)StorageApdHandler: 698: APD Handle d13a95ff-13f7e4c4 Created with lock[StorageApd0x410a50]

2014-06-14T14:39:23.132Z cpu3:33176)StorageApdHandler: 698: APD Handle 0889b40b-a5de2c02 Created with lock[StorageApd0x410a50]

2014-06-14T14:39:48.471Z cpu0:34220)WARNING: LinuxSocket: 1854: UNKNOWN/UNSUPPORTED socketcall op (whichCall=0x12, args@0xffa29d8c)

2014-06-14T14:46:35.144Z cpu2:33970 opID=454a5793)NFSLock: 1772: Failed to create lock info for lock file .lck-5600000100000000 : No connection

2014-06-14T14:46:45.167Z cpu0:33970 opID=454a5793)NFSLock: 1787: failed to remove .lck-5600000100000000

2014-06-14T14:46:45.167Z cpu0:33970 opID=454a5793)WARNING: NFSLock: 2103: Failed to create .lck-5600000100000000 : No connection

2014-06-14T14:46:45.167Z cpu0:33970 opID=454a5793)NFSLock: 2931: failed to get lock on file vsomwin_1.vmdk 0x4108a70a6570 on 192.168.143.168 (192.168.143.168): No connection

2014-06-14T14:47:11.218Z cpu0:33970 opID=454a5793)NFSLock: 1772: Failed to create lock info for lock file .lck-5500000100000000 : No connection

2014-06-14T14:47:21.239Z cpu2:33970 opID=454a5793)NFSLock: 1787: failed to remove .lck-5500000100000000

2014-06-14T14:47:21.239Z cpu2:33970 opID=454a5793)WARNING: NFSLock: 2103: Failed to create .lck-5500000100000000 : No connection

2014-06-14T14:47:21.239Z cpu2:33970 opID=454a5793)NFSLock: 2931: failed to get lock on file vsomwin_1-flat.vmdk 0x4108a70e1b00 on 192.168.143.168 (192.168.143.168): No connection

###################################################