-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement some overprovisioning protections at a storage-pool level #377
Comments
TL;DR: It's complicated 🙂 Slightly longer overview of how it currently works and hightlighting some issues: The previous statement is easy enough for an empty storage pool. However, things are getting complicated when considering The problem starts when we start to also consider actually used space, besides the reservations. With a 1TiB storage pool, That's the reason why LINSTOR takes the remaining free space of the storage pool (so in the above example the 50GiB) This might be better for the above described example, but I do agree that it does not really help with the initial scenario I guess we could improve LINSTOR by implementing both approaches, the free space based as well as the reserved space Discussions / suggestions are welcome 🙂 |
The
MaxOversubscriptionRatio
works on a per-volume basis. This means that, with for example a storage-pool 1TiB in size and a ratio of 2x, Linstor would only allow us to create a volume <2TiB in size. However, you could still create 20 resources all of which are 1TiB in size.Would it be possible for there to be some feature that prevents making an additional resource if the total aggregate size of all resource using that storage pool was to total more than 2x the storage pool size (2TiB in this example).
The text was updated successfully, but these errors were encountered: