Re: current status of zfs block_cloning on CURRENT?

2023-04-25 Thread Pete Wright
On Tue, Apr 25, 2023 at 12:35:29AM -0700, Mark Millard wrote: > Warner Losh wrote on > Date: Tue, 25 Apr 2023 04:30:26 UTC : > > > On Mon, Apr 24, 2023 at 9:49 PM Charlie Li wrote: > > > > > Charlie Li wrote: > > > > Pete Wright wrote: > > > >> i've seen a few threads about the block_cloning fe

Re: aarch64: lang/gcc1* build regression between Mar-28 and Apr-8

2023-04-25 Thread Dima Panov
Moin-moin! Some additional info. With just-cooked -current (FreeBSD 14.0-CURRENT #1 883a49e5a: Tue Apr 25 13:43:56 MSK 2023 arm64 1400088) all stable releases of GCC are unable to build with same error (gcc10, gcc11, gcc12) :( But! gcc*-devel ports builds fine, and finally I can build ann g

Re: current status of zfs block_cloning on CURRENT?

2023-04-25 Thread Pete Wright
On 4/24/23 21:30, Warner Losh wrote: On Mon, Apr 24, 2023 at 9:49 PM Charlie Li wrote: Charlie Li wrote: > Pete Wright wrote: >> i've seen a few threads about the block_cloning feature causing data >> corruption issues on CURRENT and have been keen to avoid enabling

Re: current status of zfs block_cloning on CURRENT?

2023-04-25 Thread Mark Millard
Warner Losh wrote on Date: Tue, 25 Apr 2023 04:30:26 UTC : > On Mon, Apr 24, 2023 at 9:49 PM Charlie Li wrote: > > > Charlie Li wrote: > > > Pete Wright wrote: > > >> i've seen a few threads about the block_cloning feature causing data > > >> corruption issues on CURRENT and have been keen to a