Unable to mount vSAN file share using NFSv4.1 protocol with RHEL-9.6 kernel - 5.14.0-570.16.1.el9_6.x86_64.
search cancel

Unable to mount vSAN file share using NFSv4.1 protocol with RHEL-9.6 kernel - 5.14.0-570.16.1.el9_6.x86_64.

book

Article ID: 398148

calendar_today

Updated On:

Products

VMware vSAN VMware vSAN 7.x VMware vSAN 8.x

Issue/Introduction

NFSv4.1 mount failed with the error message below:

Warning  FailedMount  5s (x6 over 21s)  kubelet MountVolume.SetUp failed for volume "pvc-########-db2c-####-bcdd-###########" : rpc error: code = Internal desc = error publish volume to target path: mount failed: exit status 32

mounting arguments: -t nfs4 -o hard,sec=sys,vers=4,minorversion=1 vsanfs1.domain.com:/vsanfs/52cf6e18-####-f541-cd09-########## /var/lib/kubelet/pods/4105152a-####-4c87-a577-####### /volumes/kubernetes.io~csi/pvc-c4acb97c-db2c-####-bcdd-##########/mount
output: mount.nfs4: mount system call failed

Environment

RHEL-9.6 kernel - 5.14.0-570.16.1.el9_6.x86_64

VMware vSAN 7.x

VMware vSAN 8.x 

Cause

Packet capture revealed that the server should return the error NFS4ERR_ATTRNOTSUPP but it is sending NFS4ERR_BADXDR (Error Code 10036) instead indicating that a file share is offline.

Frame 19: 166 bytes on wire (1328 bits), 166 bytes captured (1328 bits) ... Network File System, Ops(3): SEQUENCE PUTFH GETATTR(NFS4ERR_BADXDR) [Program Version: 4] [V4 Procedure: COMPOUND (1)] Status: NFS4ERR_BADXDR (10036)

Resolution

Update the vSAN cluster to ESXi 8.0 P05/  ESXi 8.0 Update 3e followed by vSAN File Service update which contains the fix 

Note:

 

Additional Information

During the vSAN File Service update the correct version of the VMware vSAN File Service Appliance should get downloaded automatically but if you do not have internet connectivity you can use following URL  to download the vSAN FS files 

VMware vSAN File Services Appliance 8.0U3e



for more information please refer following URLs

VMware vSAN Upgrade Best Practices
Upgrade  File Service