"The request is rejected due to many pending requests.""Unable to query vSAN Health information."ESXi: RAM disk / inode table is full."vdf -h shows the /vsantraces partition at 100% utilization.vmkwarning.log shows:2026-09-29T20:16:32.169Z -WARNING vmkwarning - [host_name] cpu1:2131061) VisorFSRam: 251: Cannot extend visorfs file /vsantraces/vsantracesIODiag--2026-09-29T########--########-####-####-####-########.zst because its ramdisk (vsantraceFailover) is full.2026-09-27T01:30:14.655Z -INFO vobd 2098072 [esx@4413 threadName="VisorfsCorrelator"] 3725011814us: [vob.visorfs.ramdisk.full] Cannot extend visorfs file /vsantraces/vsantraces--2026-09-27T01h27m35s673--6724b5b7-b14d-####-####-############.zst because its ramdisk (vsantraceFailover) is full.The default vSAN trace configuration writes to a ramdisk partition.
In ESXi 9.1.0, this is the vsantraceFailover partition.
When a persistent scratch location is not defined on the ESXi host, these traces accumulate until they exhaust the limited 300MB capacity.
Follow one of these options to resolve the issue.
For known defects, subscribe to this article (Subscribe to a Broadcom knowledge article) to receive updates on fix status.
Option A: Limit vSAN trace size on local ramdisk If additional storage is not available, run these commands via SSH on all vSAN hosts to limit trace size:
esxcli vsan trace set --urgentnumfiles=4 --urgentsize=8 --numfiles=10 --size=8esxcli vsan trace set --urgentnumfiles=10 --urgentsize=10 --numfiles=10 --size=10Option B: Redirect traces to a persistent scratch location
For vSAN 8.0 Update 1 and later, redirecting the trace path to a persistent scratch location disables persistence to the Native vSAN Trace Object and may shorten the trace retention period.
For more information, see Changing the vSAN trace destination to a persistent scratch location disables persistence to the Native vSAN Trace Object
mkdir /vmfs/volumes/####/scratch/####/vsantraces/
Followed by:
esxcli vsan trace set -f 10 -s 60 -p /vmfs/volumes/####/scratch/####/vsantraces/
esxcli vsan trace getcommand to to make sure the "VSAN Traces Directory" is updated to new location.Option C: Free up space immediately
cd /vsantracesrm vsantraces*20####*.zstNote : Some cases, ESXi syslog needs to be reloaded
esxcli system syslog reload