| Previous | Next |
| ERROR_SPACES_PROVISIONING_TYPE_INVALID | ERROR_SPACES_ENCLOSURE_AWARE_INVALID |
ERROR_SPACES_ALLOCATION_SIZE_INVALID
Allocation size belongs to the provider's virtual-disk mapping geometry
ERROR_SPACES_ALLOCATION_SIZE_INVALID reports that an explicit allocation-size value cannot be represented by the selected storage provider or pool. This setting governs how virtual capacity is allocated from the pool; it is separate from interleave, stripe width, and the file system's cluster size.
Provider implementations can impose minimum, maximum, and alignment constraints tied to metadata slabs, provisioning type, or storage tiers. Rounding a value in application code without reading the actual supported range can silently request a different geometry.
Validate units and provider constraints
- Confirm the API field's units before converting from KB, MB, or PowerShell size literals.
- Query the selected pool or subsystem for supported allocation behavior.
- Remove the explicit value and compare the provider-generated default.
- Check compatibility with Thin versus Fixed provisioning.
- Keep allocation size distinct from
Interleaveand volume allocation-unit size. - Recreate test virtual disks rather than changing production geometry experimentally.
References
- Microsoft: MSFT_StoragePool.CreateVirtualDisk
- Microsoft: New-VirtualDisk
- Microsoft: Storage Spaces concepts
Looking for a different code? Search another status or error code.