Lou Spagnuolo - 4 days ago

Hello, i encountered a problem that may be a bug (not sure). I am using windows storage spaces to combine several drives (non raid, simple strip) for a large single drive. I have 24TB total disk space using 8tb & 6Tb disks. the storage space is set up for expansion to 40TB (currently using 20TB of the actual 24tb with headroom to add additional drives to expand to 40Tb in the future).
My problem is when i create a file container on the storage space drive using NTFS and dynamic growth it works if i state max size to be 24TB but fails if i state 40TB or anything more than 24TB. BUT if i create a file container on a 4TB drive (3.6TB after formated) of the same file container for a max size of 6TB it works. Why does it create a dynamic file container larger than actual disk space on a physical drive but not in storage spaces? is this a bug?

during the creation of the file container on the 4tb drive it finishes formating and creates the file around 2.x TB. much less than the actual disk size. but on the storage space the file container veracrypt attempted to create the file beyond the availble disk space and crashes. Is there a calculation it uses for how large a dynamic file container needs to be based on the max size? I tried even creating the file container at 28TB on the storage spaces and it still crashed. i figured even at 50% size it should have completed fine.

I read the other few issues here regarding storage spaces and maybe they are similarly failing do to the sizeof the container file it is looking to create.

Thanks
Lou