Virtual Machine Disk Consolidation Failure | There is not enough space on the file system for the selected operation.
Article ID: 368604
Updated On:
Products
Issue/Introduction
Symptoms
- Virtual Machine Disk Consolidation task may show completed on the VM tasks/Events, however, the VM will continue to run on the snapshot, i.e. the vmx will still be pointing to the snapshot disk.
- Snapshot manager may also not show any snapshots in the vSphere UI(This can happen if the .vmsd file has been updated or has no snapshot hierarchy in it or the file will be empty)
vmware.log
[YYYY-MM-DDTHH:MM:SS] In(05) vcpu-0 lq993gel-1330543-auto-sink-h5:70265902-d7-18-4d3f VigorTransport_ServerSendResponse opID=lq993gel-1330543-auto-sink-h5:70265902-d7-18-4d3f seq=4945127: Completed Snapshot request with messages.[YYYY-MM-DDTHH:MM:SS] In(05) vcpu-0 lq993gel-1330543-auto-sink-h5:70265902-d7-18-4d3f Turning off snapshot info cache.[YYYY-MM-DDTHH:MM:SS] In(05) vcpu-0 lq993gel-1330543-auto-sink-h5:70265902-d7-18-4d3f Turning off snapshot disk cache.[YYYY-MM-DDTHH:MM:SS] In(05) vcpu-0 lq993gel-1330543-auto-sink-h5:70265902-d7-18-4d3f ConsolidateEnd: Snapshot consolidate complete: There is not enough space on the file system for the selected operation (5).[YYYY-MM-DDTHH:MM:SS] In(05) worker-3691024 - DISKLIB-LIB : DiskLib_IsCombinePossible: Free disk space is less than imprecise space neeeded for combine (0xce76000 < 0x4d797800, in sectors). Getting precise space needed for combine...[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - SnapshotESXCombineProgressTotal: Snapshot consolidation progress: 2[YYYY-MM-DDTHH:MM:SS] worker-3691024 - DISKLIB-LIB : DiskLib_IsCombinePossible: Insufficient space for combine. Have 110842871808 bytes, need 665501319168 bytes. <--Amount of space needed for the disk consolidation[YYYY-MM-DDTHH:MM:SS] worker-3691024 - ConsolidateCheckSpaceNeeded: Not enough space to combine source disk: '/vmfs/volumes/XXXX-c0XXXXX-b7XX-8416XXXXXXXX/INDxxxx/IND2xxxxx-000002.vmdk' and destination disk: '/vmfs/volumes/XXXX-c0XXXXX-b7XX-8416XXXXXXXX/INDxxxx/IND2xxxxx.vmdk': There is not enough space on the file system for the selected operation (-1695352563)
Environment
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x
Cause
There is not enough space on the target datastore to accommodate the change.
Resolution
Increase the capacity of the target datastore as specified in the vmware.log. The new capacity should be at least equal to or greater than the amount indicated in the log to resolve the disk consolidation issue on the Virtual Machine.
Workaround for non-OS drives: If the datastore hits the 64 TB limit, or cannot be expanded to the full size required for consolidation for any other reason, and VM must stay online, a new VM can be created on a new datastore and the data replicated from the of the original VM to the new VM, using guest OS copy functionality over the network. Once that is completed, the old VM can be removed and space can be reclaimed.
Note: This workaround would include scenarios where VMFS5 is in use and datastore space cannot be reclaimed by moving data to a new disk added to the VM because UNMAP is not supported for space reclamation on VMFS5 datastores.
Feedback
