Hello all,
I have a three node Windows Server 2012 R2 Failover Cluster running Files Services. When I enable Deduplication on an existing disk (SAN presented) it dedupes the appropriate files but doesn't release the free space afterwards. It essentially uses double the space.
The issue is even more curious when viewing the capacity of the disk through Failover Cluster Manager as the free space includes the space saving. However when viewed through explorer it's at near capacity (the doubled amount). I have viewed the disk in Treesize which agrees with FCM and shows the lower size and the majority of files residing within the System Volume Information (as expected with Dedupe).
My issue is that the physical free space is near capacity and I can't find a way to rationalise it down to the FCM/Treesize reported capacity.
I have tried:
- chkdsk
- Maintenance Mode + chkdks
- Defrag
- Failed over the resource to another node
- Run the Dedup_WeeklyScrubbing task
- Run the Dedup_WeeklyGarbageCollection task
- Run the Measure-DedupeFileMetadata cmd and the results align with FCM/Treesize
Unfortunately this issue seems a little inconsistent across our cluster as some of the disks have applied dedupe correctly and others have effectively doubled the space as discussed above. All of the disks are from the same arrays.
I'd welcome any advice on troubleshooting the issue and would be happy to provide any additional information required.
Thanks for reading!
Mark