# Budget the physical footprint before expanding an S2D volume

> How much storage-pool capacity does a planned volume expansion actually require?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-08T18:14:42+00:00
- Modified: 2026-09-08T18:23:28+00:00
- Last reviewed by DSE: 2026-09-08
- Resource type: Guide
- DSE priority: Information
- Topics: IT, Networks & Infrastructure
- Reading time: 1 minutes

## 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.

## Article

## 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](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-volumes).

## 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](https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-volumes). Source reviewed September 8, 2026.

## Primary reference

- Name: Manage volumes in Azure Local and Windows Server
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-volumes
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Budget the physical footprint before expanding an S2D volume,” DSE Security, https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.