Operational Defect Database
BugZero updated this defect 44 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 88815
vSAN 6.7 P03-P05 or vSAN 7.0 U1/U2 cluster experiences inaccessible objects or unexpected object deletion
Last update date:
4/5/2024
Affected products:
vSAN
Affected releases:
6.77.0
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Inaccessible objectsUnexpected object deletion
Cause
The symptoms may occur in the following vSAN releases due to inconsistency of the EPD database.Releases containing the defect: vSAN 6.7P03-P05vSAN 7.0 U1/U2 EPD (Entry Persistence Daemon) is a user space daemon that runs on every host that is part of the vSAN cluster. The main job of EPD is to make sure there is no component leakage when objects are deleted.The defect is due to the SQLite database used by EPD being damaged and results in objects becoming inaccessible or deleted unexpectedly.
Impact / Risks
Guests may become inaccessibleSome objects may be deleted in error
Resolution
Patch up to fixed release as soon as possible.Fixed releases: vSAN 6.7 P06+vSAN 7.0 U3c+
Workaround
Run the following command on each host in the cluster:/etc/init.d/epd stop; rm -rf /scratch/epd-store*.lock; python -c "import sqlite3; conn = sqlite3.connect('/scratch/epd-storeV2.db'); conn.execute('DELETE FROM cmmds_entries;'); conn.commit()"This does the following: Stops EPD service on all hostsDelete epd-storeV2.db on all hosts Note: DO NOT START EPD until host is patched up to a fixed buildWorkaround will prevent further harm while hosts are patched up, but cannot be used for more than 24hrsOnce above command has been run, immediately patch hosts
