Skip to content

Conversation

@Bert-Proesmans
Copy link

@Bert-Proesmans Bert-Proesmans commented Nov 5, 2025

Part of stacked pull requests to enable unmount testing. This is PR 2 out of 4. Stacks on top of #1147.

Only the last two commits apply to this specific PR.
This PR introduces new option and proper unmounting in case of encryption on ZFS volumes.

Previous PR #1147, next PR #1149
See #1140 for ealier discussion.

Closes #1139.

- Fix typo against full dataset path argument
- Make unmount with encryption keys idempotent
The value for device is copied into the SOURCE column of findmnt.
By default this is "none". The mount and unmount scripts
branch on SOURCE=fsType specifically, and the existence of "none"
in the SOURCE column causes wrong branches to be executed.
For a list of special filesystems, the default value "none"
is replaced by the value for fsType.
- Fix consistent use of fully qualified dataset path
- Add idempotent unmounting with encryption keys
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

Successfully merging this pull request may close these issues.

Unmount script on zfs-encrypted example fails at unload-key

1 participant