Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 32
Refer to the Dell Knowledge Base Article, PowerStore CLI or REST API.
View all Dell PowerStore 5200T manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 32 highlights
Issue ID MDT-152993 MDT-151804 MDT-146763 MDT-119414 Functional Area Description Workaround/Resolution Virtualization Virtualization Virtualization Virtualization A periodic, automatic cleanup process on vSphere that is performed randomly (every few days) deletes empty config vVols (directories). However, this process also deletes the ISOs folder that is pre-created by PowerStore in case you have not placed any ISO images into the folder. In a PowerStore cluster with multiple VMFS datastores that are mapped to multiple hosts, a performance impact might occur if several VMs are powered off or powered on simultaneously. During a vMotion process, some vVols are deleted. If the VASA provider becomes unavailable during a storage vMotion operation, the deletion of the vVols fails. These vVols are left orphaned and may appear as duplicates. Deploying a VM fails, and checking the vvold.log vCenter log file reveals the following messages: 2019-11-15T05:24:35.161Z info vvold[2112740] [Originator@6876 sub=Default] VVolAbandonedObjectScan::ProcessNamesp ace examining namespace /vmfs/volumes// Recreate the ISOs folder using the following PowerStore CLI command: pstcli -service storage_container -id create_directory -size 100G -name ISOs By default PowerStore creates a 500 GB folder, but you can specify another size if necessary. Refer to the Dell Knowledge Base Article 000320477: Best practices for VMFS datastores - for Bootstorm or Failover with VMware SRM. Delete the orphaned vVols using PowerStore CLI or REST API. Try to deploy the VM again. For more information, see the Dell Knowledge Base Article 000132277 PowerStore: VM deployment can fail with "A general system error occurred." and 2019-11-15T05:24:35.318Z warning vvold[2112740] [Originator@6876 sub=Libs] 2112740:VVOLLIB : VVolLib_OpenObjectTrackingFile:11348: VVolLib_OpenObjectTrackingFile: Failed to open object tracking file /vmfs/volumes// /.vvolObjList with error 6 where is the UUID of the storage container and is the alphanumeric identifier of the config-vVol of the VM. 32 Known Issues