Alexander Motin 3583fa38e8 ZVOL: Restrict cloning with different properties ...

While technically its not a problem to clone between ZVOLs 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.

This is a replica of #18180 from FS.

Reviewed-by: Ameer Hamza <ahamza@ixsystems.com>
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Alexander Motin <alexander.motin@TrueNAS.com>
Closes #18315

2026-03-12 18:30:58 -07:00

..

avl

Prefer VERIFY0P(n) over VERIFY(n == NULL)

2025-08-07 11:41:37 -07:00

icp

Fix check for .cfi_negate_ra_state on aarch64

2026-03-06 11:04:37 -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

FreeBSD: Improve dmesg kernel message prefix

2026-03-09 10:17:23 -07:00

zcommon

Convert all HAVE_<name> SIMD gates to HAVE_SIMD(<name>)

2026-03-05 15:01:37 -08:00

zfs

ZVOL: Restrict cloning with different properties

2026-03-12 18:30:58 -07: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

Add simd_config.h and HAVE_SIMD() selector

2026-03-05 15:01:42 -08:00

Makefile.bsd

Add simd_config.h and HAVE_SIMD() selector

2026-03-05 15:01:42 -08:00

Makefile.in

Fix --enable-invariants on FreeBSD

2026-01-14 14:54:12 -08:00