@Choonster said in Strange behaviour from new hard drive:
@cvi said in Strange behaviour from new hard drive:
@Choonster said in Strange behaviour from new hard drive:
I still have no idea what's using this space, but I'm going to try enabling and then disabling compression for all the files on the drive (most of them had the "compressed" flag copied from the old drive).
Could it be that this is some sort of staging area used for the compression? I.e., compression is expensive, and happens slowly in the background (and for some reason, Windows keeps the original data around until compression succeeds)?
Does this change if you leave the PC idle for a few hours?
It could be something like this.
I used the PowerShell script below to enable compression for the whole drive a day or two ago, and when I checked
fsutil
recently the Total Reserved Clusters figure was down to about 3 GB. I ranrobocopy
again after and it tried and failed to copy a new file to the drive. When I checkedfsutil
again just now, Total Reserved Clusters was down to 51.2 MB.So some combination of enabling compression and leaving it idle seems to have freed up this missing space.
Get-ChildItem H:\ -Recurse | ForEach-Object { compact /C $_.FullName }
Hi, I just bought a new WD My Book 4TB, and I also encounter this Total Reserved Clusters problem. Although, mine is not as big as yours, only 4.7 GB, currently.
Did you finally find a solution to this problem?
Can you let me know?