{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "slug": "dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume", "url": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/" }, "title": "Budget the physical footprint before expanding an S2D volume", "summary": "How much storage-pool capacity does a planned volume expansion actually require?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "network-infrastructure", "label": "Networks & infrastructure", "alt": "Resilient network core with engineered blue and gold data paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "slug": "networks-infrastructure", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-08T18:14:42+00:00", "modified_at": "2026-09-08T18:23:28+00:00", "reviewed_on": "2026-09-08", "reading_minutes": 1, "word_count": 193, "potentially_affected": "Administrators expanding volumes on Storage Spaces Direct clusters.", "dse_recommendation": "Write the logical-size request and physical-capacity calculation separately.", "primary_source": { "name": "Manage volumes in Azure Local and Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-volumes", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Manage volumes in Azure Local and Windows Server. Source reviewed September 8, 2026.

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nWrite 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Manage volumes in Azure Local and Windows Server. Source reviewed September 8, 2026.", "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nIdentify 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.\n\n## DSE recommendation\n\nWrite 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.\n\n## Verification\n\nAfter 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.\n\n## Official references\n\n[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." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "url": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-08" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Budget the physical footprint before expanding an S2D volume", "item": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "url": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/", "headline": "Budget the physical footprint before expanding an S2D volume", "description": "How much storage-pool capacity does a planned volume expansion actually require?", "abstract": "How much storage-pool capacity does a planned volume expansion actually require?", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nIdentify 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.\nDSE recommendation\nWrite 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.\nVerification\nAfter 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.\nOfficial references\nMicrosoft Learn: Manage volumes in Azure Local and Windows Server. Source reviewed September 8, 2026.", "datePublished": "2026-09-08T18:14:42+00:00", "dateModified": "2026-09-08T18:23:28+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260908-149-budget-the-physical-footprint-before-expanding-an-s2d-volume/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Budget the physical footprint before expanding an S2D volume" }, "articleSection": [ "IT", "Networks & Infrastructure" ], "keywords": [ "IT", "Networks & Infrastructure", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" }, { "@type": "Thing", "name": "Networks & Infrastructure", "url": "https://update.dsesecurity.com/topic/networks-infrastructure/" } ], "wordCount": 193, "timeRequired": "PT1M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Manage volumes in Azure Local and Windows Server", "url": "https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/manage-volumes" } } ] } }