There was multiple issues about sending from nonencrypted to encrypted dataset (#605, #565).
Main problem is that it is not possible rollback encrypted dataset on zfs recv.
Fast workaround is return from function createDataSet before call zfs create. Dataset is than created on zfs recv without need to rollback. This is issue even when sending from encrypted to encrypted (#601, #495, #302)
What is the reason to explicitly create dataset before zfs recv?
Second problem is that compressed feature add "-Lce" but -e is incompatible with recv to encrypted dataset. Proposed fix is add new feature disableEmbedded which removes "-e" from options added by compressed feature.
As a new feature it will be backward compatible.
I am not perl programmer so it should be considered as draft or proof of concept.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
There was multiple issues about sending from nonencrypted to encrypted dataset (#605, #565).
Main problem is that it is not possible rollback encrypted dataset on zfs recv. Fast workaround is return from function createDataSet before call zfs create. Dataset is than created on zfs recv without need to rollback. This is issue even when sending from encrypted to encrypted (#601, #495, #302)
What is the reason to explicitly create dataset before zfs recv?
Second problem is that compressed feature add "-Lce" but -e is incompatible with recv to encrypted dataset. Proposed fix is add new feature disableEmbedded which removes "-e" from options added by compressed feature. As a new feature it will be backward compatible.
I am not perl programmer so it should be considered as draft or proof of concept.