Deletion of virtual machine folder from vVol datastore fails with "Invalid argument" error.
search cancel

Deletion of virtual machine folder from vVol datastore fails with "Invalid argument" error.

book

Article ID: 371269

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

++Listing vm directory fails with "Invalid argument" error.

[root@esxi_name:/vmfs/volumes/vvol:863211baa4c63c5a-xxxxxxxxxxxxxxxx] ls -ltrha VM_Name
ls: VM_Name: Invalid argument


++Deleting the vm Folder or its object fails with "Invalid argument" error.

[root@esxi_name:/vmfs/volumes/vvol:863211baa4c63c5a-xxxxxxxxxxxxxxxx] rm -rf VM_Name
rm: can't stat 'VM_Name': Invalid argument

++Deleting the VM or its folder from VC UI reports "Object was not found" error.

Environment

vSphere7.x
vSphere8.x

Cause

rfc4122.17025cac-3ee3-xxxx-92af-xxxxxxxxxxxx > VM_Name

Regarding above Config VVOL, the Array is reporting that this config VVOL exist while we are querying it..


2024-06-25T18:20:54.533Z info vvold[3169169] [Originator@6876 sub=Default] VasaOp::QueryVirtualVolumeInt [#169390]: ===> Issuing 'queryVirtualVolume' to VP [Datastore_name:Connected (Outstanding 0/5)]
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] VasaOp[#169390] ===> FINAL SUCCESS queryVirtualVolume VP (Datastore_name) Container (863211ba-xxxx-3c5a-b7e3-xxxxxxxxxxx) timeElapsed=7 msecs (#outstanding 0)
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.fefcb73f-xxxx-42ed-b0b8-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.c707e77d-xxxx-4f46-9831-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.1b867166-xxxx-416f-9512-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.b86ab73a-xxxx-423d-9219-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.e2a56ca7-xxxx-4ac9-bee4-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.d072c7bc-xxxx-428c-a489-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.219b317e-xxxx-4884-996c-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.82060806-xxxx-4a78-a5c4-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.ff4151ca-xxxx-448b-a6ee-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.3e97b30f-xxxx-483f-84ff-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.33d58f39-xxxx-4708-9d07-xxxxxxxxxxx
2024-06-25T18:20:54.541Z info vvold[3169169] [Originator@6876 sub=Default] QueryVirtualVolumeInt vvolUuid = rfc4122.17025cac-xxxx-4f53-92af-xxxxxxxxxxx

++While trying to open the object, array is failing it with InvalidArgument. This indicates object does not exist on the vvol array.

2024-06-25T18:20:58.531Z info vvold[3169182] [Originator@6876 sub=Default] Came to SI::BindVirtualVolume: esxContainerId 863211ba-a4c6-xxxx-b7e3-xxxxxxxxxxxx VVol Id rfc4122.17025cac-3ee3-xxxx-92af-xxxxxxxxxxxx bindType Normal (isConfigVvol: true)
2024-06-25T18:20:58.531Z info vvold[3169182] [Originator@6876 sub=Default] VasaOp::BindVirtualVolume [#169437]: ===> Issuing 'bindVirtualVolume' to VP [Datastore_name:Connected (Outstanding 0/5)]
2024-06-25T18:20:58.665Z info vvold[3169182] [Originator@6876 sub=Default] VasaOp[#169437] ===> FINAL SUCCESS bindVirtualVolume VP (Datastore_name) Container (863211ba-a4c6-xxxx-b7e3-xxxxxxxxxxxx) timeElapsed=134 msecs (#outstanding 0)
2024-06-25T18:20:58.665Z error vvold[3169182] [Originator@6876 sub=Default] SI:BindVirtualVolume@3467 VASA bind for VVol (rfc4122.17025cac-3ee3-xxx-92af-xxxxxxxxxxxx) returned error : INVALID_ARGUMENT ()

We encountered below issue while trying to access a virtual volume (VVOL).

  • A specific VVOL was found by the vSphere when it queried the storage array.
  • However, attempting to bind this VVOL resulted in an error message indicating the object doesn't exist.

Due to this problem, vSphere cannot access the VVOL, preventing its deletion.

Resolution

This situation might be due to a known issue with a particular Storage firmware version. In such cases, the array may incorrectly report the existence of VVOLs that are not actually available.

We recommend contacting Storage Vendor support to investigate:

  • Why the "bind" operation fails despite the VVOL supposedly existing.
  • Why the array reports the VVOL's existence if it's actually missing.
Powered by Wolken Software