|Article Number: 503348||Article Version: 4||Article Type: Break Fix|
When the available capacity of a Storage Resource Pool (SRP) in a VMAX3 or VMAX All Flash reaches the Reserved Capacity value, active or new extent copies (XCOPY) can take a long time to complete and may cause VMware tasks to timeout.
This problem is caused when the Reserved Capacity is reached. The root of the issue is the SRP running out of available capacity. The Reserved Capacity is set at 10% by default so when the SRP exceeds 90% used capacity, the extent copy sessions (along with replication in general) are impacted.
Note that the Reserved Capacity setting is a safety measure designed to prevent copy operations like XCOPY, SnapVX, Clone, and RDF/A DSE from using up all of the available capacity of an SRP. Essentially, when the limit is reached, only host writes are able to allocate the remaining free capacity. Without the Reserved Capacity, the SRP could reach its maximum unhindered, and essentially halt the array.
A code resolution is currently being developed to change the behavior of the XCOPY sessions in this situation, however there are also manual steps that can be taken to resolve.
The primary resolution to the issue is to increase the available space in the SRP so that the Reserved Capacity is not breached. In a VMware environment this might include running manual UNMAP against existing datastores to free space on the array.
If space cannot be found, the recommendation is to disable XCOPY on the VMware ESXi hosts so that host copy is used instead. XCOPY can be re-enabled after space is made available. Details on how to disable XCOPY dynamically can be found in this white paper: http://www.emc.com/collateral/hardware/white-papers/h8115-vmware-vstorage-vmax-wp.pdf