Permission and ownership modifications made to a vSAN File Service share do not persist across vSAN File Service node reboots or failover events.
search cancel

Permission and ownership modifications made to a vSAN File Service share do not persist across vSAN File Service node reboots or failover events.

book

Article ID: 450199

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

 

  • Permission and ownership modifications made to a vSAN File Service share do not persist across vSAN File Service node reboots or failover events.

  • When a vSAN File Service share is mounted via NFS v4.1 with Kerberos security (sec=krb5p) on a Linux client (such as RHEL 8):

    • Ownership or permission changes applied to the share's root directory handle revert back to the original mounting user context following a restart or failover of a vSAN File Service VDFS node.

    • Multi-user access permissions and custom ownership settings are lost post-failover, impacting workload persistence.

 

 

Environment

vSAN 8.x

vSAN 9.x

Cause

This behavior is a known issue.

Resolution

This issue is resolved in the following releases:

  • ESXi 8.0 Update 3 Patch 10 (or later)

  • ESXi 9.2 (or later)

To resolve this issue, upgrade the affected ESXi host(s) to ESXi 8.0 Update 3 Patch 10 or ESXi 9.2.