Good News if you use ESXi 5.0 or ESXi 5.1 – the CBT Bug is fixed for these versions.
Unfortunately there is no fix available at the moment for ESXi 4.x and 5.5.
If you do not know about this issue you can read my previous post or VMware KB 2090639: QueryChangedDiskAreas API returns incorrect sectors after extending virtual machine vmdk file with Changed Block Tracking (CBT) enabled
Here you can find the patch for
- ESXi 5.0: VMware ESXi 5.0, Patch Release ESXi500-201412001 (2088715)
- ESXi 5.1: VMware ESXi 5.1 Update 3 Release Notes
If you use ESXi 4.0 or 5.5 you can only use the following workarounds for the issue:
- perform a Storage vMotion after having extended the CBT-enabled disks past a 128 GB boundary
- or you disable and re-enable CBT after extending past the boundary:
- turn off CBT
- take a snapshot
- delete the snapshot
- turn on CBT
- take one more snapshot
- last but not least delete the snapshot
according to vmware support there is a fix available for ESXi 5.5 (http://kb.vmware.com/kb/2096281)