HCI/S2D Reserve capacity - Why is this not just automactic?

Jim Gandy 121 Reputation points
2021-04-26T17:48:09.307+00:00

This is a problem for many of us. We run out of space in the Storage Pool and we do not know there is a problem until a disk fails or we see storage repair jobs failing. Is there a technical reason why Microsoft is not able to just reserve the equivalent of one capacity drive per server, up to 4 drives automictically at Storage Pool creation as described here
https://learn.microsoft.com/en-us/windows-server/storage/storage-spaces/plan-volumes#reserve-capacity?

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
358 questions
0 comments No comments
{count} votes

7 answers

Sort by: Most helpful
  1. Steven Ekren 166 Reputation points
    2021-04-29T17:30:51.463+00:00

    @Reeves, Louis There are 2 things you note. Pool reserve space and volume space. When you create a new volume with storage spaces it allocates a fixed amount of space from the storage pool. The reserve capacity of the storage pool is there to allow for a physical disk to fail and be able to start a rapair of the virtual disks (storage spaces/volumes) before the disk is replaced or brought back. You can allocate volumes and fill the stroage pool without a reserve and the only effect is repairs will only take place when the physical disks are all there.

    What I believe you are referencing is running out of space on a volume. This is no different on storage spaces as any other disk exposed in Windows Server. The volume has a specific amount of space and if it gets filled up, it's filled until you can extend the volume or reduce the data in the volume. This is not storage spaces specific, any volume on any windows system is the same. There are tools out there that will monitor volume free space. Windows Admin Center in the cluster view, shows volumes and makes clear how much free space is there.

    I hope this helps,
    StevenEk@Microsoft.com

    1 person found this answer helpful.
    0 comments No comments

  2. Reeves, Louis 1 Reputation point
    2021-04-26T17:50:03.36+00:00

    I also posted the similar question. I just noticed your post- so this is hopefully not going to become common- Hope MS will plan something for this-

    https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_repair/why-azure-stack-hci-s2d-hcios-reserve-capacity-is/e6be231b-60ac-4463-b171-76c24cf1f78a?tm=1619459006776

    0 comments No comments

  3. CyrAz 5,181 Reputation points
    2021-04-26T21:09:35.41+00:00

    Because it's your absolute right to fill up all the space you have. But in that case you need to be able to quickly replace a failed drive...

    0 comments No comments

  4. Steven Ekren 166 Reputation points
    2021-04-28T23:45:29.287+00:00

    https://learn.microsoft.com/en-us/windows-server/failover-clustering/health-service-faults

    The following fault should be discoverable via Windows Admin Center, or by the PowerShell for getting faults described in that article. This is the description of the fault that shows:

    Pool Capacity (1)
    FaultType: Microsoft.Health.FaultType.StoragePool.InsufficientReserveCapacityFault

    Severity: Warning  
    Reason: "The storage pool does not have the minimum recommended reserve capacity. This may limit your ability to restore data resiliency in the event of drive failure(s)."  
    RecommendedAction: "Add additional capacity to the storage pool, or free up capacity. The minimum recommended reserve varies by deployment, but is approximately 2 drives' worth of capacity."
    
    0 comments No comments

  5. Jim Gandy 121 Reputation points
    2021-04-29T01:27:23.097+00:00

    Is there an event in the event logs for this information?

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.