'General vSAN error' while removing the disk from vSAN diskgroup

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• Removing the disk from a vSAN disk group may fail with 'General vSAN error'.
  
  

• Removing the disk via ESXi CLI using the command 'esxcli vsan storage remove -u <vSAN_disk_UUID>' will report below error.

  Unable to remove device: Failed to get VsanInfo operation lock for diskOplock, an operation is currently in progress (locked pid: 0), error: /tmp/.vsanDiskOpLock.lock. LOCK: timeout waiting for lock after 30 seconds. Lock is currently held by process 2101612 (vsanmgmtd: vsanmgmtd -s -c /etc/vmware/vsan/vsanmgmt-config.xml)

   

Environment

VMware vSAN 7.x

Cause

This issue can be caused by the vsanmgmtd daemon running out of allocated memory resources.
vsanmgmtd is a daemon that runs on ESXi and is responsible for multiple aspects of configuration, management and monitoring of vSAN-enabled hosts.


var/run/log/vsanmgmtd.log from the affected vSAN host will report 'Memory pressure' events.

2025-06-16T07:38:10.098Z info vsand[2101612] [opID-MainThread statsdaemon ::_ logDaemonMemoryStats] Daemon memory stats: eMin-150.924MB, eMinPeak-172.336MB, rMinPeak-179.236MB MEMORY PRESSURE
2025-06-16T08:08:13.969Z info vsand[2101612] [opID-MainThread statsdaemon ::_ logDaemonMemoryStats] Daemon memory stats: eMin-150.924MB, eMinPeak-172.336MB, rMinPeak-179.236MB MEMORY PRESSURE


Resolution

To fix the vsanmgmtd memory leak issue, upgrade both vCenter and ESXi to version 7.0U3c or later.

Please find the below article for your reference:
vSAN Management (vsanmgmt service) memory leak issue


Workaround:

• Restart the vsanmgmtd service to clear stale memory state:

  /etc/init.d/vsanmgmtd status
/etc/init.d/vsanmgmtd restart

   

• Once restarting the vsanmgmtd service, the disk removal operation will complete successfully.

Note: Workaround is only a temporary fix for this issue, and the vsanmgmtd memory issue may reoccur if the environment is not upgraded to the fix version or later.