| Type | Suffix | Writable | Sparse | Purpose | |------|--------|----------|--------|---------| | | -flat.vmdk | Yes | No | Primary, pre-allocated disk | | Delta VMDK | -delta.vmdk | Yes | Yes | Snapshot/linked clone changes | | Sparse VMDK | .vmdk (no suffix) | Yes | Yes | Thin-provisioned primary disk | | Base VMDK | .vmdk + -flat.vmdk | No* | Varies | Parent for snapshots (*read-only when child exists) |

delete a delta VMDK file directly from the datastore using the file browser. This will corrupt the VM. Always use the snapshot manager or vmware-cmd to delete/consolidate snapshots.

Instead of modifying the original flat VMDK file, VMware freezes the parent disk and creates a new, sparse file (the delta). All new writes go to this delta file. Reads, however, must check both the delta (for recent changes) and the parent (for unchanged data).

Consolidating a delta VMDK means committing its changes back into the parent VMDK:

John realized that delta VMDKs were powerful tools, but they required careful management to prevent issues like this. He made a mental note to regularly monitor snapshot activity and consolidate them in a timely manner.