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

future of snap_reserve? #54

Closed
okrause opened this issue Nov 29, 2021 · 1 comment
Closed

future of snap_reserve? #54

okrause opened this issue Nov 29, 2021 · 1 comment

Comments

@okrause
Copy link
Contributor

okrause commented Nov 29, 2021

The provider allows to set the volume option snap_reserve. snap_reserve allows to hide a given percentage of space from the user. A 10 TiB volume with 20% snap_reserve will only show 8 TiB to the user (e.g. via df).

Unfortunately, a lot of space reporting counters start to become unreliable as soon as snap_reserve <> 0 is set. 0 is the default and setting it to something else might cause issues for users. Fortunately, very, very few users seem to use it so far.

I want to have a discussion:

  • Should we remove that option to protect users from potential issues?
  • Should we put explicit warnings in the documentation so users are warned?
  • Should we remove it from the documentation and hide it, so only experienced pro-users will use it? Issue is likely auto-generated documentation.

Opinions?

@carchi8py
Copy link
Collaborator

We will combine all the snap_reserve stories in to #55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants