• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Any way to get disk space usage closer to file size on disk?

Penth

Senior member
I've got a computer with just under 3GB of files on it, but windows reports that disk usage is at around 7GB. I want to make an acronis image of the drive and put it onto a HD that is only 3GB in size (the drive will not be used, and will only be plugged in if we need to get something off of this image). Is there any way without a reformat to get the disk usage closer to the total size of the files stored on the drive? I know windows has some overhead, but in this case it's like 130%.
 
Sounds odd that it would differ that much. I would think 7GiB would compress pretty well and acronis would take all those files and get them under 3GiB since that is what they really are.
 
There's got to be something taking up all the extra space. I'd try to find some type of file/folder analysis tool and see where all that space is going.

My "C" drive has 34,000 files on it. 13.1GB in size and size on disk is also 13GB.
 
If you are going to C: and selecting all files/folders to find the space usage, well remember there is a hidden folder called "System Volume Information" that has all the system restore points. Then there is the windows swap file which is also hidden, and if you have hibernation enabled that is another hidden file.

For example, if I select all the visible files/folders in C: and hit properties it only says 6-ish GB. After showing all files/folders it is 9.8GB because of the restore points, swap file, and hibernation file.
 
Hi, Are you counting all the hidden files that you can't see? One way would be to partition the drive into smaller chunks. The overhead will become smaller as the Cluster Size will be reduced. Jim
 
Sounds like the file format is FAT32. If it is, you can convert it to NTFS by running convert from the command prompt.
 
Back
Top