Skip to content

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

Description

@smklein

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Sled AgentRelated to the Per-Sled Configuration and ManagementnexusRelated to nexusstorageRelated to storage.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions