Reszed disk does not reflect the proper size from vSphere client

I used a procedure to shrink the .VMDK file which was 200GB as we did not need the space allocated to it and there was plenty of free space. I used one of the recommended methods to shrink the volume from within windows disk management creating un-allocated space and then subsequently using the vi interface through an SSH session to reduce the size of the disk. It worked perfectly fine and I can see the disk size reduced on Disk Management from within the windows to 100GB. But when I logon to vSphere client to check the size of the .VMDK file it is unchanged and still stating the size as 200GB. How can i ensure it reflects the changed size?

Regards
Ven
Venkatesh SrikantiahAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
No problems, please don't forget to select a solution and award points, and close out.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
A number of methods, move the disk to another datastore, remove the disk from the VM, and re-add it back (do not delete from disk).

Has the size changed on the datastore - this is key ?

I assume a bit like this method I wrote in this EE Article

HOW TO: Shrink a VMware Virtual Machine Disk (VMDK) in 15 minutes
0
 
Venkatesh SrikantiahAuthor Commented:
Yes, That was your article I used to follow the procedure to Shrink a VMDK file. The removing and adding the disk work perfectly fine, Thanks for your quick reply.

Regards
Ven
0
 
Venkatesh SrikantiahAuthor Commented:
Great job
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.

All Courses

From novice to tech pro — start learning today.