Date: Wed, 12 Apr 2023 10:43:27 -0700 From: Mark Millard <marklmi@yahoo.com> To: Cy Schubert <Cy.Schubert@cschubert.com>, dev-commits-src-main@freebsd.org Cc: vishwin@freebsd.org Subject: Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 Message-ID: <EBC430EF-90B6-41C1-957F-BD15113041B2@yahoo.com> In-Reply-To: <72115147-BA5F-44CA-9DD5-D84CC4BE626F@yahoo.com> References: <72115147-BA5F-44CA-9DD5-D84CC4BE626F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Just a resend to fix a typo in the CC.] From: Cy Schubert <Cy.Schubert_at_cschubert.com> wrote on Date: Wed, 12 Apr 2023 16:54:59 UTC : > . . . > > You need to copy from/to the same dataset to reproduce the problem. Copying from a source dataset to a different dataset will avoid block_cloning. https://openzfs.github.io/openzfs-docs/man/7/zpool-features.7.html reports: QUOTE block_cloning . . . . . . Blocks can be cloned across datasets under some conditions (like disabled encryption and equal recordsize). This feature becomes active when first block is cloned. When the last cloned block is freed, it goes back to the enabled state. END QUOTE I've no clue if that is/will--be different for FreeBSD for some reason. === Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EBC430EF-90B6-41C1-957F-BD15113041B2>