2016-02-14 11:39 PM
I have an 8 blade Windows Hyper-V 3 cluster. Each of these blades has access to a 5.00Tb LUN (Cluster Shared Volume), created through Snapdrive, stored in a 5Tb volume, where each of my 80-odd virtual machines' vhdxs are stored:
Storage efficiency is enabled, and after the last run, these are the results:
However, Windows still reports only 439Gb of free space:
I don't have any snapshots or QoS setup on this volume.
Where did the other 718Gb go that's supposed to be left in the LUN?
How much can I safely decrease the size of the volume now that it is deduped?
Solved! SEE THE SOLUTION
2016-02-15 02:29 AM
Chances are there that VMware had not reclaimed the free blocks due to which you have the size difference. Use the VMware reclaim tool to resolve this issue http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=2014849
Hope this helps.
2016-02-15 02:34 AM
I'm using Hyper-V, which means I use the Space Reclamation tool in Snapdrive.
However, when invoking the tool, this is displayed:
So space reclamation won't make a difference.
2016-02-15 06:23 AM
2016-02-15 12:35 PM
Yes, he is correct. If order to "see" the real available space, you would need to use CIFS shares over SMB 3.0 for your Hyper-V storage. This way, NetApp's WAFL is handling the underlying filesystem instead of Windows and it has visibility into the actual free space. It has other added benefits as well, take a look at http://www.netapp.com/us/media/tr-4172.pdf for more details.
2016-02-15 03:07 PM