I have a thick virtual disk (vmdk) file that is purely just a file-store. I currently have it configured to take up 2TB, however, there is only one 900GB partition on it. I read somewhere that the following command will force it to shrink, however, the poster said that this way is "fraught with danger":
vmkfstools -X 910G /vmfs/src_file.vmdk --force
Will this render my data innaccessible? I am only downsizing the vmdk file to free up the unpartitioned space in the ESXi datastore. Using the VMWare Tools shrink utility does not shrink the disk, it prepares it and then immediatelyn says the operation completed successfully.
You can always create a new virtual disk, mount both on your guest, copy the files over, mount the new smaller disk in place of the old larger disk. Once you are happy everything is right, delete the old larger disk.
If you're running any recent version of esx(i) you can do a storage vmotion and convert it from thick to thin as it goes.
If you're on 4.x this is built in to the gui, if it's a previous version it either involves getting a plug-in or using powershell.
You will need two datastores with the second at least large enough to store the entire vmdk plus associated files (swap, nvram, etc). But you could move it right back after you're done.
This is a completely supported way of doing things and is safe.