Skip to content
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

Dataset upper bound should be non-optional, enforced #1630

Open
smklein opened this issue Aug 22, 2022 · 0 comments
Open

Dataset upper bound should be non-optional, enforced #1630

smklein opened this issue Aug 22, 2022 · 0 comments
Labels
nexus Related to nexus Sled Agent Related to the Per-Sled Configuration and Management storage Related to storage.

Comments

@smklein
Copy link
Collaborator

smklein commented Aug 22, 2022

Datasets within Omicron have a field dedicated to their "Maximum provisioned size":

/* An upper bound on the amount of space that might be in-use */
size_used INT
);

This field is:

It currently exists as an approximation of crucible dataset size for allocation purposes, but it limited from the perspective of enforcing disk space availability.

We should be implementing / enforcing this for all dataset types. #1231 starts attempting to enforce out-of-space errors, but is incomplete without this cooperation across dataset types.

@smklein smklein added storage Related to storage. Sled Agent Related to the Per-Sled Configuration and Management nexus Related to nexus labels Aug 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
nexus Related to nexus Sled Agent Related to the Per-Sled Configuration and Management storage Related to storage.
Projects
None yet
Development

No branches or pull requests

1 participant