Date: Wed, 12 Apr 2023 11:14:53 -0700 From: Cy Schubert <Cy.Schubert@cschubert.com> To: Mark Millard <marklmi@yahoo.com>, dev-commits-src-main@freebsd.org Cc: vishwin@freebsd.or Subject: Re: git: 2a58b312b62f - main - zfs: merge openzfs/zfs@431083f75 Message-ID: <DA7BAD0E-E57E-4676-8F94-9A6B2E2D43D9@cschubert.com> In-Reply-To: <72115147-BA5F-44CA-9DD5-D84CC4BE626F@yahoo.com> References: <72115147-BA5F-44CA-9DD5-D84CC4BE626F.ref@yahoo.com> <72115147-BA5F-44CA-9DD5-D84CC4BE626F@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On April 12, 2023 10:41:17 AM PDT, Mark Millard <marklmi@yahoo.com> wrote: >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 > Looking at the patch on GH, this would also affect linux. -- Cheers, Cy Schubert <Cy.Schubert@cschubert.com> FreeBSD UNIX: <cy@FreeBSD.org> Web: https://FreeBSD.org NTP: <cy@nwtime.org> Web: https://nwtime.org e^(i*pi)+1=0 Pardon the typos. Small keyboard in use.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DA7BAD0E-E57E-4676-8F94-9A6B2E2D43D9>