Unable to migrate VMs on a vVOLs datastore

Products

• VMware vSphere ESXi

Issue/Introduction

• vMotion or cold migration fails only for VMs on vVOLs datastore(s).
• The vVOLs datastore(s) show size as 0 B on vCenter UI and ESXi UI.
• The vVOLs datastore(s) failed to be browsed on vCenter UI, ESXi host UI and ESXi host SSH.
  • Important note: To browse a vVOL datastore through an ESXi host SSH, it is not recommended to use the command "ls", as it might cause ESXi to be stuck for a long time to list the directories in a vVOL datastore. The workaround suggested is to use the "/usr/lib/vmware/osfs/bin/osfs-ls" command to list the content of vVOL datastores. For more information, please check Browsing vVOL Datastore from ESXI Shell.
• The VASA provider related to the vVOLs datastore(s) has "Rescan-error" seen in its status when checked from the vSphere client: 
  • vCenter > Configure > Storage Providers.

Environment

VMware vCenter Server (All versions).

Resolution

1. Check the status and configuration of the VASA provider on the storage side to be sure it is healthy. Please engage the storage vendor if needed.
2. Re-register the VASA provider on vCenter by following one of the options below:

For vCenter 7.0.x

• Be sure to have the Storage Provider authentication information.
• In the Storage Providers tab, Remove the impacted VASA provider from vCenter and Add it again using the Storage Provider's credentials.

For vCenter 8.0.x

• In the Storage Providers tab, find the impacted VASA provider.
• Click on the 3 dots on the left of the VASA provider's name.
• Click on Re-authenticate vCenter Server and when the wizard appears on the screen, fill it with the Storage Provider's credentials and click Save.