vswp objects in inaccessible state

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• From vSAN Skyline health there is alarm for "vSAN Object Health - Inaccessible objects"

 

• 'VIEW DETAILS' will show the inaccessible objects as 'Unknown' and Type as 'Other'.
  
  
  
  
  
• To verify the details of the inaccessible objects, use the below command from the Host CLI:
  
  
  • To list all the inaccessible objects:
    'esxcli vsan debug object list -health=inaccessible'

• • To verify the details of a specific inaccessible object.
    'esxcli vsan debug object list -u <Object UUID>
    
    
    

Sample command output:

Object UUID: ########-####-####-####-############
   Version: 15
   Health: inaccessible - Lost quorum.(APD)
   Owner: Host-A
   Size: 0.00 GB
   Used: 0.00 GB
   Policy: 
   Configuration: 
      
      RAID_1
         Component: ########-####-####-####-############
           Component State: ACTIVE,  Address Space(B): 0 (0.00GB),  Disk UUID: ########-####-####-####-############,  Disk Name: naa.################
           Votes: 1,  Capacity Used(B): 12582912 (0.01GB),  Physical Capacity Used(B): 4194304 (0.00GB),  Host Name: Host-A
         Component: ########-####-####-####-############
           Component State: ABSENT,  Address Space(B): 0 (0.00GB),  Disk UUID: ########-####-####-####-############,  Disk Name: naa.################
           Votes: 1,  Host Name: Host-B
         Witness: ########-####-####-####-############
           Component State: ABSENT,  Address Space(B): 0 (0.00GB),  Disk UUID: ########-####-####-####-############,  Disk Name: naa.################
           Votes: 1,  Host Name: Host-C

   Type: vmswap
   Path: /vmfs/volumes/vsan:######-####-####-####-########/######-####-####-####-########/VM name.vswp (Exists)

Environment

VMware vSAN 7.x
VMware vSAN 8.x

Cause

Inaccessible vswp objects could be due to the result of some failure happened in the vSAN cluster. These objects are non-critical, do not impact running virtual machines, and are automatically recreated when required.

vswp objects are temporary and generated when VMs are powered on, the failure interrupted their normal lifecycle leaving only the owner components Active and the others Absent.

Some of the common reason for the presence of inaccessible vswp object are:

• Hosts are in vSAN Decom/ESXi maintenance mode
• Failed disks/disk groups
• Network partition
• vSAN cluster shutdown/restart is in an inconsistent state.

 

Resolution

If only vswp objects are in inaccessible state, you can follow the below steps to remove it:

• Login to the vCenter UI.
  
  
• Navigate to: vSAN Cluster > Monitor > Skyline Health > vSAN Object Health
  
  
• Click on 'Purge inaccessible objects' to remove the stale vswp objects.
  
  

If the inaccessible vswp objects are not removed by following the above steps, ,please reach out to Broadcom Support for assistance.

Additional Information

vSAN Health Service - Data Health – vSAN Object Health