What you need to know
How much storage-pool capacity does a planned volume expansion actually require?
Potentially affected
Administrators expanding volumes on Storage Spaces Direct clusters.
DSE recommendation
Write the logical-size request and physical-capacity calculation separately.
Source facts
Microsoft requires sufficient pool capacity for the expanded volume’s physical footprint. Its three-way-mirror example doubles a 1 TB logical volume to 2 TB, increasing the physical footprint from 3 TB to 6 TB. An S2D volume consists of multiple stacked objects, including its partition, virtual disk, and applicable storage tiers. Resizing requires updating several of those objects. Microsoft documentation.
Applicability
Identify the volume, resiliency, tiers, current footprint, free pool capacity, and desired logical size. Review the documented procedure and any media-specific capacity requirements before changing the volume.
DSE recommendation
Write the logical-size request and physical-capacity calculation separately. Have the storage owner check the available pool space and approve the workload maintenance plan. Preserve the original object sizes and confirm that additional capacity, if needed, will be added through a supported method.
Verification
After the approved expansion, compare the sizes of the relevant objects and the filesystem’s usable capacity with the plan. Test representative workload access and review remaining pool capacity. Record a partially expanded stack or unexplained footprint as a failure to resolve before another storage change.
Official references
Microsoft Learn: Manage volumes in Azure Local and Windows Server. Source reviewed September 8, 2026.
Review the official source
Manage volumes in Azure Local and Windows Server · Verified September 8, 2026
Need help applying this guidance safely?
DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.
Talk with DSE