NetApp VSC 2.1.1 may corrupt VMDK file

[PeterDA]

Hi,
für alle die dies das Tool einsetzen:

Space reclamation feature in VSC 2.1.1 may corrupt VMDK file

Summary
An issue in VSC 2.1.1 has been identified wherein the Provisioning & Cloning space reclamation feature may corrupt a VMDK file that has been extended. The NTFS bitmap file that accounts for the file system layout on a VMDK file that has been extended can become fragmented. When fragmentation occurs, VSC 2.1.1 can read past the end of the first run of the bitmap into user data, improperly identifying holes in the VMDK file.

Users Affected
Any VSC 2.1.1 environment matching the following criteria may be affected by this issue:
• Using the VSC Provisioning & Cloning Space Reclamation feature
• Having VMDKs that have been extended past their original size

Problem Description
When creating an NTFS partition on a VMDK, a special bitmap file is created that keeps track of the allocation of each cluster in the file system. If the NTFS partition is extended, the size of the bitmap file must also grow. When the VMDK file grows larger than its original size, it is possible that the bitmap file may become fragmented. Because of this fragmentation, VSC may not properly read the bitmap and can reclaim space for clusters that are actually allocated.

Workaround
Do not use the space reclamation feature on any VMDK that has been extended past its original size. Once VSC 2.1.2 has been released, it will be safe to use the space reclamation feature on any VMDK, including VMDKs that have been extended.

Gruß Peter