Castlewood
asked on
Huge difference for the free space shown on Hyper-V host and on VM itself.
On the Hyper-V host (Pic 1 and Pic 2), we have a volume called “Volume2” containing 4 x 4TB HDs (mirrored) -- so the total capacity is about 7.27 TB. This volume2 provides for nothing but the VM file server “BUD” – with the following two VHDX files:
Bud.vhdx (2012R2 OS) : about 52.35GB of max 80GB (dynamic)
Bud_Data.vhdx (for Data): about 4.49TB of max 7.27TB (dynamic)
So we can do a math and figure the free space of Volume2 is roughly about 2.67TB as shown on Pic 1.
But if we go into the VM’s drive properties and Disk Management, we can see the free space of that drive is about 4.58TB. That is a huge difference. Can you please educate me why and what could be wrong?
Bud.vhdx (2012R2 OS) : about 52.35GB of max 80GB (dynamic)
Bud_Data.vhdx (for Data): about 4.49TB of max 7.27TB (dynamic)
So we can do a math and figure the free space of Volume2 is roughly about 2.67TB as shown on Pic 1.
But if we go into the VM’s drive properties and Disk Management, we can see the free space of that drive is about 4.58TB. That is a huge difference. Can you please educate me why and what could be wrong?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
answered
ASKER
For the over-subscription issue David brought out, I got an question... Isn't it right the data loss by over-subscription issue shall NOT occur until the free space is running out? Look the volume2 providing for BUD.vhdx and BUD_Data.vhdx has about 2.67TB free space while BUD.vhdx is actually just with 80GB in size, which is over-subscribed. The large free size should be able to accommodate the very small over-subscription? Yes or No??
In another word, should I avoid over-subscription whatsoever in a dynamic expanding environment ?