A general system error occurred: Launch failure. Cause: Out of resource.2025-12-16T10:34:15.520Z Wa(180) vmkwarning: cpu11:70121116)WARNING: SwapExtend: 703: Current swap file size is 0 KB.2025-12-16T10:34:15.520Z Wa(180) vmkwarning: cpu11:70121116)WARNING: SwapExtend: vm 70121116: 707: Failed to extend swap file. type=regular from 0 KB to 81920 KB. currently 0. status=No space l
2025-12-23T05:21:02.093Z In(182) vmkernel: cpu26:88136083)Fil3: 11066: Max no space retries (10) exceeded for caller Fil6_FileIOInt (status 'No space left on device')2025-12-23T05:21:02.094Z In(182) vmkernel: cpu26:88136083)Fil6: 4289: '9d009c66-1478-5e55-b032-############': Fil6 file IO (<FD c7 r11>) : No space left on device2025-12-23T05:21:02.094Z In(182) vmkernel: cpu26:88136083)Fil6: 4251: ioCtx: 0x45ba3c9f1f40, world: 88136083, overallStatus: No space left on device, token: 0x0, tokenStatus: N, txnToken: 0x0, txnTokenStatus: N, totalIOSize: 1048576, maxIOLength: 102666240
VMware vSAN
vMotion fails when the VM folder usage reached 255GB, which the maximum size for a vSAN namespace object.
For example:-
'du -h' command output from the VM folder shows the overall folder usage as 255GB and there are multiple stats folder consuming space.[root@ESXi_host01:/vmfs/volumes/vsanDatastore/9d009c66-1478-5e55-b032-############] du -h1.0M ./.sdd.sf256.0K ./.dvsData/50 37 33 e9 c5 6f d4 7c-fd a1 70 66 17 ae d0 3d384.0K ./.dvsData1.4G ./stats-92.5G ./stats-832.0G ./stats-760.2G ./stats-662.3M ./stats-5156.6G ./stats-4557.8M ./stats-32.7M ./stats-23.4M ./stats-164.0M ./stats-0156.3M ./stats255.0G . ------------->> Overall VM folder usage