You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: