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
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
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
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 it
> >> until the dust settles. i was under the impression
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 it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but w
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 it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but when i ran "zpool
u
hi everyone,
i've seen a few threads about the block_cloning feature causing data
corruption issues on CURRENT and have been keen to avoid enabling it
until the dust settles. i was under the impression that we either
reverted or disabled block_cloning on CURRENT, but when i ran "zpool
upgrade
