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

Esxi Windows 2008 Changes itself from Thin to Thick

I have a Windows 2008 SP2 Std VM in ESXi that has changed itself from thin provisioning to thick.  At first I thought it was something I did.  I have a base machine that is thin.  I use converter standalone to do V2V and make sure the new machine is thin.  

Then, I do updates, reboot here and there and somewhere along the way it changes itself to thick.  I've repeated it a few times today thinking I must be mistaken.  At this piont I'll live with it, but would like to know why so I can learn.   Perhaps I can prevent it next time.

Thanks
0
craig40not
Asked:
craig40not
  • 5
  • 3
  • 2
2 Solutions
 
Paul SolovyovskyCommented:
Have you baslined this issue by creating a brand new VM in thin  mode? What version of ESXi are you running?
0
 
za_mkhCommented:
How do you know the disk has changed to thick??
0
 
za_mkhCommented:
If you right click the VMDK in the datastore using the VI Client, do you get an Inflate option (that is not greyed out)? If it is not greyed out, the disk is still thin .. Well that's a quick way I use to work out why type of VMDK it is...
0
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
craig40notAuthor Commented:
Thanks everyone for following up.

I am on the latest version (whatever that is.  I'm not at that location right now).  It was just set up last week.

If I look at the settings for that VM and select the hard drive from the first tab, it says thick where it used to say thin.

I'll see if I have an inflate option in the datastore when I get back to that location.
Will post what I find then.
0
 
craig40notAuthor Commented:
Sorry paulsolov, I failed to follow up on the first question.  I have not tried to see if this happens from a clean initial setup.  This is happening on the client I create from V2V from my clean setup.  I didn't want to ruin my clean machine.  Do you think it would matter?
0
 
Paul SolovyovskyCommented:
I was just looking to baseline, shouldn't matter though.  
0
 
craig40notAuthor Commented:
When I  got to Edit Settings and select Hard Disk on the hardware tab, the provisioned size shows 40GB. Both the 40 and the GB in different boxes are disabled.  

I looked at the vdmk in the datastore, right clicked and inflate is NOT greyed out.  Being curious, I clicked inflate thinking I'd get a yes/no dialog to continue and guess what...it didn't prompt but instead inflated my 17GB vdmk to 40GB.  Don't know why I did that.  Guess it is like picking a scab when you are a kid.  

So, does that mean it wasn't thick but now it is?  If I run out of space and want to make it larger, will it be possible later even though ithe size is greyed out?

0
 
craig40notAuthor Commented:
By the way, after having inflated, inflate is now greyed out.  
0
 
Paul SolovyovskyCommented:
Looks like it was thick.  Easy way to check is to see what the th vmdk file is.  If it's the full 40GB than it's now thick if it's only the approx. size of your data in the vmdk then it has to be thin.
0
 
craig40notAuthor Commented:
Thanks everyone.  Still not sure why the size and thick/thin are disabled.  But I guess it doesn't matter now.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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