XtremIO Family: Unable to reclaim space from ESX host

           

   Article Number:     499221                                   Article Version: 6     Article Type:    Break Fix 
   

 


Product:

 

XtremIO Family,XtremIO HW Gen2 400GB,XtremIO HW Gen2 400GB Encrypt Capbl,XtremIO HW Gen2 400GB Encrypt Disable,XtremIO HW Gen2 400GB Exp Encrypt Disable,XtremIO HW Gen2 400GB Expandable,XtremIO HW Gen2 800GB Encrypt Capbl

 

Issue:

 

 

The unmap command (space reclamation) does not work/reclaim any space from the XtremIO when there is a VPLEX in between them.                                                           

 

 

Cause:

 

 

There are few possible reasons for the issue:   
   
    1. VPLEX version does not support reclamation   
    2. Volume settings do not allow reclamation   
    3. Host may not have re-scanned volumes after VPLEX configuration changes
                                                           

 

 

Resolution:

 

 

Verify if the environment allows reclaiming by checking the following criteria:   

         
  •         VPLEX  5.5 SP1 (Supports UNMAP for basic local VPLEX)     
  •      
  •         VPLEX 5.5 SP2 and later – supports complete UNMAP for XtremIO (including Local Mirroring and Metro) – For more information check VPLEX Release notes     
  •      
  •         ESXi 5.0 Update 1 and later     
  •      
  •         Make sure the “delete status” for the volume is supported     
  •    
           Delete status - unsupported   
   
    If unsupported, check the volume settings and make sure the volume you are trying to reclaim space from is “thin capable true” and “thin enabled enabled”. This can be verified from the VPLEX CLI by issuing the following command:   
        
VPlexcli:/> ls -t /clusters/*/virtual-volumes/<Vplex volume name goes here>::thin-capable/clusters/cluster-2/virtual-volumes/Local_DD_Leg1_1_vol:        Name          Value      ------------  -----------        thin-capable  trueVPlexcli:/> ls -t /clusters/*/virtual-volumes/<Vplex volume name goes here>::thin-enabled/clusters/cluster-2/virtual-volumes/Local_DD_Leg1_1_vol:        Name          Value      ------------  -----------       thin-enabled  disabled    
   
    This can be also verified from the GUI interface. Access the link below for an article and video instructions:   
    https://community.emc.com/community/products/vplex/blog/2016/04/22/complete-unmap-support-for-xtremio    
   
    If disabled, change the volume setting to enabled by issuing the following command:   
        
     
VPlexcli:/clusters/*/virtual-volumes/<Volume name> set thin-enabled trueVPlexcli:/> ls -t /clusters/*/virtual-volumes/<Volume name>::thin-enabled/clusters/cluster-2/virtual-volumes/Local_DD_Leg1_1_vol:       Name          Value     ------------  -----------      thin-enabled  enabled      
     
      After changing the settings to thin enabled enabled, the volume(s) must be rescanned by the ESX host. It may take a few minutes before the re-scan is complete.     
          
    Check once again for the “delete status” option and verify that it is now supported. Try running the reclamation (either from VSI plugin or by the UNMAP command (https://support.emc.com/kb/334268).   
   
    If you are still experiencing errors, a manual reclamation may be executed. Check the XtremIO Host and Configuration Guide for more information about that.   
   
    https://support.emc.com/docu56210_XtremIO-Host-Configuration-Guide.pdf?language=en_US                                                           

 

 

Notes:

 

 

Reference notes:   
   
    The following article contains a video on how to use space reclamation when an XtremIO array is behind a VPlex. It also shows how to check volume settings from the VPlex GUI interface.   
   
    https://community.emc.com/community/products/vplex/blog/2016/04/22/complete-unmap-support-for-xtremio   
   
   
    Here are VMware KB's about space reclamation:   
   
    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057513       
       
        https://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2014849
   
   
   
    Here is an EMC KB about space reclamation:   
   
    https://support.emc.com/kb/334268