VM files seen on the source datastore after storage vmotion from one VVol datastore to another

Products

• VMware vCenter Server

Issue/Introduction

Symptom:

• After storage vmotion, some leftover files can be seen on the source datastore. VM is only pointing to the target datastore.

Validation:

• Errors seen in "/var/run/log/osfsd.log" -

2025-03-11T07:12:16.157Z info osfsd[213600900] [Originator@6876] 213600900:VVOLLIB : VVolLib_IpcStorageFaultToVVolLibError:766: Storage Fault STORAGE_FAULT (22): The server is currently unable to handle the request. A service is not running or is not reachable. If the condition persists, contact Nimble Storage Support.
2025-03-11T07:12:16.157Z warning osfsd[213600900] [Originator@6876] 213600900:VVOLLIB : VVolLibProcessTaskUpdate:2334: VASA task (arrayID:'NimbleStorage:1b121655d5ae7e3f', task:'d2878c3d-f44a-4813-8157-e1a91e7cde42') has completed with FAILURE: (STORAGE_FAULT, The server is currently unable to handle the request. A service is not running or is not reachable. If the condition persists, contact Nimble Storage Support.) The VVol target encountered a vendor specific error
2025-03-11T07:12:16.157Z warning osfsd[213600900] [Originator@6876] 213600900:VVOLLIB : VVolLibExecuteVasaTask:3501:  Task of type 0x5ca1ab1e failed (retval: The VVol target encountered a vendor specific error)
2025-03-11T07:12:16.157Z error osfsd[213600900] [Originator@6876 sub=Vvol] VVolCreateObject@2164:Failed to create Config VVOL SF-C1B-DMZ154 CID 00000002-0000-4001-8b12-1655d5ae7e3f
2025-03-11T07:12:16.157Z info osfsd[213600900] [Originator@6876 sub=Ipc opID=m7yp7f4d-243591-auto-57yg-h5:70013779-6c-01-af-af3f] FINISH Ipc request on provider [    vvol], container 0000000200004001-8b121655d5ae7e3f, aliasID: 0000000200004001-8b121655d5ae7e3f, bufferSize: 0x75F for CREATE, status: I/O error.

2025-03-11T07:18:31.618Z cpu73:2106428 opID=cefc8463)VVol: 2301: [vvolDev: rfc4122.e3680279-515c-4b35-ad83-b0c065b83329] Failed to issue command 0x26 (Address is not aligned on required boundary)

Environment

VMware vSphere ESXi 7.x

VMware vSphere ESXi 8.x

Cause

• Issue needs to be investigated by the storage vendor since the events in osfsd log highlights that the VASA task has failed since either the server is currently unable to handle the request or a service is not running or is not reachable.

Resolution

• Please investigate the issue further with the storage vendor.
  
  Note: Restarting storage services can fix the issue, however implement this only after storage vendor's suggestion.