Loading...
Loading...
PPDM VM backup using Transparent Snapshot Data Mover (TSDM) failed to enable Lightweight Delta (LWD) with error: SPIF filters change failure: There is not enough space on the file system for the selected operation. Failed to attach IO Filter vmwarelwd: Not enough space. Error observed in the vmdm.log : vmdm.2025-11-18.0.log.gz: 2025-11-18T16:09:36.884Z WARN [] [vpe-thread-30] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:95b087f4b01285e5;JOB_ID:b0cf7bd99757cfed][] [c.e.b.v.v.u.SdmEnableProtectUtil.configureProtect(468)] - Unable to ENABLE LWD on VM1 vmdm.2025-11-18.0.log.gz: 2025-11-18T16:09:36.884Z WARN [] [vpe-thread-30] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:95b087f4b01285e5;JOB_ID:b0cf7bd99757cfed][] [c.e.b.v.v.u.SdmEnableProtectUtil.configureProtect(481)] - DpSetProtection error message: SPIF filters change failure: There is not enough space on the file system for the selected operation..Failed to attach IO Filter vmwarelwd: Not enough space. vmdm.2025-11-18.0.log.gz: 2025-11-18T16:09:36.884Z WARN [] [vpe-thread-30] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:95b087f4b01285e5;JOB_ID:b0cf7bd99757cfed][] [c.e.b.v.v.a.VPEConfigureOp.logErrorStack(64)] - Unable to configure VM1 com.emc.brs.vmdm.error.ComponentException: Unable to ENABLE LWD on VM1 - SPIF filters change failure: There is not enough space on the file system for the selected operation..Failed to attach IO Filter vmwarelwd: Not enough space. Error observed in the hostd.log : 2025-12-11T16:00:26.353Z Db(167) Hostd[2103011]: [Originator@6876 sub=Vigor.Vmsvc.vm:/vmfs/volumes/vsan:526449e6c4e52e2c-b061ce834a2b2d76/9d009c66-1478-5e55-b032-043201487020/VM1.vmx] Set disk SPIFs message: SPIF filters change failure: There is not enough space on the file system for the selected operation. 2025-12-11T16:00:26.353Z Db(167) Hostd[2102982]: --> Failed to attach IO Filter vmwarelwd: Not enough space. Verified the ESXi has enough space on the datastore and memory. The backend datastore is vSAN. Tried to vMotion the VM to a different host. The vMotion failed with error: A general system error occurred: Launch failure. Cause: Out of resource The vmkernel.log reports 'No space left on device' for the object '9d009c66-1478-5e55-b032-043201487020' : 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-043201487020': Fil6 file IO (<FD c7 r11>) : No space left on device 2025-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 Universally Unique Identifier (UUID) '9d009c66-1478-5e55-b032-043201487020' belongs to namespace object for the affected VM 'VM1' : root@host01:/] localcli vsan debug object list -u 9d009c66-1478-5e55-b032-043201487020 Object UUID: 9d009c66-1478-5e55-b032-043201487020: ...... Type: vmnamespace Path: /vmfs/volumes/vsan:526449e6c4e52e2c-b061ce834a2b2d76/VM1 (Exists) Group UUID: 9d009c66-1478-5e55-b032-043201487020 Directory Name: VM1 The VM1 VM folder is 255 GB, which is the default maximum size for the vSAN namespace: [root@host01:/vmfs/volumes/vsan:526449e6c4e52e2c-b061ce834a2b2d76/9d009c66-1478-5e55-b032-043201487020] du -h 1.0M ./.sdd.sf 256.0K ./.dvsData/50 37 33 e9 c5 6f d4 7c-fd a1 70 66 17 ae d0 3d 384.0K ./.dvsData 1.4G ./stats-9 2.5G ./stats-8 32.0G ./stats-7 60.2G ./stats-6 62.3M ./stats-5 156.6G ./stats-4 557.8M ./stats-3 2.7M ./stats-2 3.4M ./stats-1 64.0M ./stats-0 156.3M ./stats 255.0G .
The VM folder is at 255 GB, which is the vSAN namespace limit.
Engage VMware support to free up the space of the VM folder.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.