Best Oscillating Tool Shootout - 25 Models Tested - Duration: 10:36. Pro Tool Reviews 32,158 views. I have an rhel 6.1 guest os running on VMware workstation (9.0.2 build-1031769) hosted on Windows 7 Enterprise 64 bit. The size of the vmdk file is around 65 GB whereas the total size of the guest os is only 11GB.

Thin provisioned disks are a great feature to save capacity as you virtual machines filesystem will never use the full capacity. I do not know a single system where you do not have at least 10GB of free space for OS disks. I am not considering databases, applications or fileservers which will grow constantly. Having thin provisioned disk is usually so it is a valid design choice even in production. A common issue with thin disks is that the size will grow when required, but never shrink. When you require the capacity only once you might want to get it back from the virtual machine. This post describes how to reclaim unused space from the virtual machine.

Virtual Machine Preparation (Windows) Windows does not automatically zero deleted blocks. Microsoft provides a tool that can zero blocks after while deleting a file or zero out the entire free space. This is required to reclaim space back from the virtual disk.

Cracks and serial numbers. • Download • run sdelete.exe -z [Drive] Wait a couple of minutes until the process is finished. Please note that you virtual disk file (VMDK) will grow to the full size during the process. Virtual Machine Preparation (Linux) Linux does not zero deleted blocks too. There are various tools available to create zeroed blocks.

The best known tool is dd which should be available on all systems. • Identify free space with df • Fill the free space with dd vma:/mnt/data # df -h vma:/mnt/data # dd bs=1M count=8192 if=/dev/zero of=zero This will zero 8GB of the available 8.2GB (1MB Blocksize * 8192 = 8GB). Please note that you virtual disk file (VMDK) will grow to the full size during the process. Shrink VMDK File • Power off the Virtual Machine, or disconnect the virtual Disk you want to shrink • Connect to the ESXi Host with SSH • Navigate to the Virtual Machine Folder • Verify disk usage with du • Run vmkfstools -K [disk] • Verify disk usage with du root@esx3:/vmfs/volumes/ds1/vma $ du -h vma_1-flat.vmdk 7.9G vma_1-flat.vmdk root@esx3:/vmfs/volumes/ds1/vma $ vmkfstools -K vma_1.vmdk vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 Hole Punching: 25% done. Root@esx3:/vmfs/volumes/ds1/vma $ du -h vma_1-flat.vmdk 1.9G vma_1-flat.vmdk. It is a common notation that the short and a long command is in the documentation and in manpages. Using both does not work: [root@esx4:/vmfs/volumes/57604a1d/pixel] vmkfstools -K --punchzero pixel.vmdk Failed to open virtual disk '--punchzero': The system cannot find the file specified (25) [root@esx4:/vmfs/volumes/57604a1d/pixel] vmkfstools --punchzero pixel.vmdk vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 Hole Punching: 0% done. [root@esx4:/vmfs/volumes/57604a1d/pixel] vmkfstools -K pixel.vmdk vmfsDisk: 1, rdmDisk: 0, blockSize: 1048576 Hole Punching: 0% done.

Vmfs-tools Introduction Originally loosely based on the, this set of tools has since evolved to handle more features from VMFS, such as extents, and allows to access VMFS through the standard Linux VFS with the help of the FUSE framework. While it is still work in progress and is not destined for production use yet, it can be of some help for some people. Authors vmfs-tools is developped by Christophe Fillot and Mike Hommey. License vmfs-tools is free software/open source, distributed under the terms of the or any later version.

Download • (md5sum: 5a50e1bc071939adb7a33e56369de652) • • Availability A vmfs-tools package is available in. It is also known to be. Build and install instructions To get a full build of vmfs-tools, you need the following prerequisites: • gcc • GNU make • libuuid's development files • pkg-config • libfuse's development files • asciidoc • xsltproc • docbook-xsl From the above list, only the first three are strictly required. The lack of libfuse's development files will result in the vmfs-fuse program not being built. The lack of asciidoc, xsltproc or docbook-xsl will result in no manual pages (though you can still look at the.txt files within the source tarball). Building vmfs-tools should be as simple as running ` make' or ` gmake`, depending on how GNU make's binary is named on your system.

To install vmfs-tools, just run ` make install' (or ` gmake install'). The install location for the binaries is $prefix/sbin, $prefix/share/man for the manual pages, where $prefix is /usr/local by default.