vSAN Skyline Health -- File Service - Share Health

Products

• VMware vSAN

Issue/Introduction

This article explains the File Service - Share Health in the vSAN Skyline Health and provides details on why it might report an error.

For more information on vSAN Skyline Health - File Service tests, see:

• vSAN Health Service - File Service - Infrastructure health
• vSAN Health Service - File Service - File Server Health

Environment

VMware vSphere 7.0.x

Resolution

Q: What does File Service - Share Health check do?

It checks if the file service share is in a good state.

Q: What does it mean when it is in an error state?

The column 'Reason' will provide the detail error message which can be referred to the following table.
 

Check Item	Error Message Type
Share Health	No backing vSAN object found for this file share, or the VDFS daemon for this file share is not working
	Used capacity of this share exceeds the soft quota
	Backend vSAN objects are not compliant with non-availability related policies
	Storage policy contents of this share has been reconfigured and does not match anymore

 

Q: How does one troubleshoot and fix the error state?

No backing vSAN object found for this file share, or the VDFS daemon for this file share is not working:

1. Check VDFS daemon status on the Host on which the File Share is located by:

1.1 Identify Host by viewing the File Share
1.2 Check the status of the VDFS Daemon on the Host

 

2. Check the Health Status of the related vSAN Object of the File Share
By reviewing File Share Objects Health 
or by reviewing the general vSAN Object Health in Skyline Health


Used capacity of this share exceeds the soft quota:

Alarm refers to File Share usage.
The Alarm can be resolved by either moving/removing some files from the File Share
or reconfiguring the File Share with a larger soft quota (= Edit a File Share )

Backend vSAN objects are not compliant with non-availability related policies

Check the storage policy is compliant for the backing object.

 

Storage policy contents of this share has been reconfigured and does not match anymore.

Reconfigure the storage policy of the file share.