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

Handle evolutive layouts #244

Closed
immae opened this issue May 23, 2023 · 2 comments
Closed

Handle evolutive layouts #244

immae opened this issue May 23, 2023 · 2 comments

Comments

@immae
Copy link
Contributor

immae commented May 23, 2023

This is a feature request.

Currently disko layout creation happens only in oneshot at "initialization": if we want to rearrange the layout after creation we need to do the action manually, and reflect that in the disco configuration for mounting, with the risk of not exactly replicating the changes.

The generic case is probably impossible to handle, and probably not worth the trouble (changing the layout of a disk is not something that happens everyday), but there are two things that could have an added value:

  • Some cases (creation of zfs datasets "on-the-fly") could have an "easier" implementation and a quite useful addition

  • Other ones could make some checks during activation and verify (best effort) that the layout corresponds to the declared one and show a warning otherwise. This would permit "incremental" computation of a diff between declared and current, until the diff is complete enough to be turned into a set of actions to enforce it.

I’d be interested in participating in starting that kind of development (for ZFS at first for instance ;) ) if that’s part of the wanted direction for that tool

@dehnert
Copy link

dehnert commented Sep 26, 2024

I think this is a duplicate of #295 , which was partially implemented in #568 .

@iFreilicht
Copy link
Contributor

Agreed, thank you!

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

3 participants