mirror_zfs/man/man7
oromenahar 121924575e Allow block cloning across encrypted datasets
When two datasets share the same master encryption key, it is safe
to clone encrypted blocks. Currently only snapshots and clones
of a dataset share with it the same encryption key.

Added a test for:
- Clone from encrypted sibling to encrypted sibling with
  non encrypted parent
- Clone from encrypted parent to inherited encrypted child
- Clone from child to sibling with encrypted parent
- Clone from snapshot to the original datasets
- Clone from foreign snapshot to a foreign dataset
- Cloning from non-encrypted to encrypted datasets
- Cloning from encrypted to non-encrypted datasets

Reviewed-by: Alexander Motin <mav@FreeBSD.org>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Original-patch-by: Pawel Jakub Dawidek <pawel@dawidek.net>
Signed-off-by: Kay Pedersen <mail@mkwg.de>
Closes #15544
2024-01-08 16:11:39 -08:00
..
dracut.zfs.7 contrib: dracut: fix race with root=zfs:dset when necessities required 2023-03-31 09:47:48 -07:00
vdevprops.7 Configure zed's diagnosis engine with vdev properties 2023-01-23 13:14:25 -08:00
zfsconcepts.7 zfsconcepts: add description of block cloning 2023-10-07 09:08:20 -07:00
zfsprops.7 Add '-u' - nomount flag for zfs set 2023-10-03 15:41:46 -07:00
zpool-features.7 Allow block cloning across encrypted datasets 2024-01-08 16:11:39 -08:00
zpoolconcepts.7 Remove implication that child disks aren't vdevs in zpoolconcepts(7) 2023-09-19 08:52:06 -07:00
zpoolprops.7 Add support for zpool user properties 2023-04-21 10:20:36 -07:00