Hi all,
I'm using the Windows 10 feature "Storage Space" to create a software raid of disparate drives to create unified storage space. When I'm on the "This PC" view in DOpus I only get the capacity of one the drives that make up this space - 3.63 TB instead of 10 TB. It doesn't strictly matter in the sense that Windows reports the correct size, and right now I'm nowhere near filling the thing up, but it does mean that DOpus reports the drive half full when in fact it is about 20 % full.
We just report what GetDiskFreeSpaceEx tells us is available. So Windows is telling us only 3.63 TB is free on that logical drive.
GetDiskFreeSpaceEx reports the space that is available to the user, so if user quotas are being applied to the drive then it would only report how much your account is allowed to write to the drive, not the total free space on the drive. I don't know if that explains things or not.
I cannot find any information on any other APIs in Windows (other than the older GetDiskFreeSpace, which is no good) or anything special that should be done when querying Storage Space drives. If Storage Space works correctly then it should be invisible to application-level software like Opus.
(Edit: Total Capacity comes via the same API. Presumably both the Free and Total values are wrong for you on this drive?)
Yup, and when it comes to it Windows Explorer is wrong too. The only accurate amount is in the Manage Storage Spaces window, where you can see the combined space of all the drives:
Thanks anyway,
B
PS. Hmm, thinking about it, maybe the pool capacity is the total capacity of the drives, but that amount of free space is after the RAID overhead?
If Explorer is also wrong then that's just what Windows thinks the space on the drive is, I guess. Maybe there is a quota in effect?
I did a quick test in a VM using two 20 GB drives pooled into a single 40 GB drive (no resiliency etc. as that would halve the space), and Opus and the shell both report the same, correct size and free space:
