• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1270
  • Last Modified:

ESX Thick to Thin still same size

I have a virtual server that was a 60gb thick disk. I used vmotion to move it to another datastore and changed it from thick to thin but its still 60gb on the datastore but inside the vm its only using 30gb of the 60gb disk. How can i get the vmdk to size down to just the used space like thin is suppose to work. This is on vmware ESX 4.0
0
cisconoshut
Asked:
cisconoshut
  • 3
  • 2
  • 2
  • +3
2 Solutions
 
Paul SolovyovskySenior IT AdvisorCommented:
rescan the controller and/or refresh the VI Client.
0
 
cisconoshutAuthor Commented:
that makes no difference the size is still 60gb on the datastore.
0
 
ppdogsCommented:
was this machines HDD any time filled up to close to 60Gb?
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
cisconoshutAuthor Commented:
Yes its also a p2v.
0
 
bgoeringCommented:
Take a look at the summary page for the Virtual machine - under resources does it show a difference between provisioned size and used storage? Or in the Datastore browser a difference between Size and Provisioned Size?

Often it is a VM that has been around for a while, space won't be reclaimed if it isn't set to binary zeros. There is a Microsoft Sysinternals tool that (for Windows anyway) called sdelete (http://technet.microsoft.com/en-us/sysinternals/bb897443.aspx) that will clear unused space to binary zeros - then another storage vmotion to thin will reclaim all that unused space.

Usage: sdelete -c c:
if c: is the drive to reclaim

If it isn't a Windows OS let me know what it is. I believe I found such a tool for Linux at one time but off the top of my head I can't recall what it is.

Good Luck

 
0
 
Danny McDanielClinical Systems AnalystCommented:
are you using NFS storage by chance?
0
 
ppdogsCommented:
as bgoering said. if it was full one time even if the files were deleted vmware may not be able to see any clear white spaces. defrag and zero the emprty space and try.
0
 
Danny McDanielClinical Systems AnalystCommented:
you could cat out the descriptor file to verify that the disk is actually supposed to be thin.  It should have the line ddb.thinProvisioned = "1" within it.  See http://virtualbox-provenpractice.blogspot.com/2009/04/thick-disk-to-thin-disk.html if you are unsure how to do this.
0
 
bgoeringCommented:
You should not even have to defrag (though that is not a bad idea for other reasons) if all you want to do is recover the physical disk space. If you do decide to defrag, do it before zero the unused space otherwise you will have used space wherever defrag moved files or file fragments around.
0
 
chkdsk01Commented:
You will need to reclaim that storage space.  Because the disk was originally thick, all 60 GB was allocated.  Then you converted it to thin....  The thick to thin conversion does just that, convert.  It does not reclaim the 30 GB of "empty" space.  Check out this article.
http://www.virtualizationteam.com/virtualization-vmware/vsphere-virtualization-vmware/vmware-esx-4-reclaiming-thin-provisioned-disk-unused-space.html 
0
 
cisconoshutAuthor Commented:
Thanks so much that solved my issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now