Alexander Motin aa29455dd7 Restrict cloning with different properties ... While technically its not a problem to clone between datasets with different properties, it might create expectation of new properties being applied during data move, while actually it won't happen. For copies and checksum it may mean incorrect safety expectations. For dedup, compression and special_small_blocks -- performance and space usage. New zfs_bclone_strict_properties tunable controls it. Reviewed-by: Rob Norris <robn@despairlabs.com> Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Signed-off-by: Alexander Motin <alexander.motin@TrueNAS.com> Closes #18180		2026-02-10 09:53:24 -08:00
..
avl	Prefer VERIFY0P(n) over VERIFY(n == NULL)	2025-08-07 11:41:37 -07:00
icp	icp: emit .note.GNU-stack section for all ELF targets	2026-01-08 09:21:12 -08:00
lua	SPDX: license tags: MIT	2025-03-13 17:56:54 -07:00
nvpair	nvpair: chase FreeBSD xdrproc_t definition	2026-01-28 21:41:33 -05:00
os	zfs_vnops_os.c: Move a vput() to after zfs_setattr_dir()	2026-02-10 09:29:37 -05:00
zcommon	Add snapshots_changed_nsecs dataset property	2026-01-06 09:36:20 -08:00
zfs	Restrict cloning with different properties	2026-02-10 09:53:24 -08:00
zstd	Zstd: Document update policy	2026-01-20 13:41:24 -08:00
.gitignore	FreeBSD: Ignore symlink to i386 includes	2022-08-02 16:34:23 -07:00
Kbuild.in	Zstd: Integrate v1.5.7 into the ZFS build system	2026-01-20 13:41:06 -08:00
Makefile.bsd	Zstd: Integrate v1.5.7 into the ZFS build system	2026-01-20 13:41:06 -08:00
Makefile.in	Fix --enable-invariants on FreeBSD	2026-01-14 14:54:12 -08:00