Use the available drive count to calculate the size of each allocation. - #146
Merged
Conversation
Signed-off-by: Anthony Floeder <anthony.floeder@hpe.com>
matthew-richerson
approved these changes
Aug 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adjusted the spare allocation policy to use the number of drives available at the time that a storage pool is created.
Tested with 16 and 15 drives.
16 drives
create 16000000000000 -> 1000000000000 bytes/drive
15 drives
create 16000000000000 -> 1066666672128 bytes/drive -> adjusted capacity 16000000081920
15 drives
create 15000000000000 -> 1000000000000 bytes/drive