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.

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

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35

32
Known Issues
Issue ID
Functional Area
Description
Workaround/Resolution
MDT-152993
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.
Recreate the ISOs folder using the
following PowerStore CLI command:
pstcli -service storage_container -id <id
where to create the folder>
create_directory -size 100G -name ISOs
By default PowerStore creates a 500 GB
folder, but you can specify another size if
necessary.
MDT-151804
Virtualization
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.
Refer to the Dell Knowledge Base Article
000320477: Best practices for VMFS
datastores – for Bootstorm or Failover
with VMware SRM.
MDT-146763
Virtualization
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.
Delete the orphaned vVols using
PowerStore CLI or REST API.
MDT-119414
Virtualization
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/<storage-container-
identifier>/<vvol-identifier>
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/<storage-container-
identifier>/<vvol-identifier>
/.vvolObjList with error 6
where <storage-container-identifier> is the
UUID of the storage container and <vvol-
identifier> is the alphanumeric identifier of
the config-vVol of the VM.
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.”