Re: ZFS txg rollback: expected timeframe?

On Tue, Oct 31, 2023 at 1:15 PM John F Carr <jfc@mit.edu> wrote:

>
>
> > On Oct 31, 2023, at 06:16, Alexander Leidinger <
> alexleidingerde@gmail.com> wrote:
> >
> > Issue: a overheating CPU may have corrupted a zpool (4 * 4TB in raidz2
> setup) in a way that a normal import of the pool panics the machine with
> "VERIFY3(l->blk_birth == r->blk_birth) failed (101867360 == 101867222)".
> >
>
> I disabled that assertion because it gives a false alarm with some
> combinaion
> of deduplication, cloning, and snapshotting on one of my systems.
>
> See
>
>  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538
>  https://github.com/openzfs/zfs/issues/11480


I don't have deduplication on this pool. There are clones, and
snapshots, and there could be recent ones if poudriere does some. Is it
still a false alarm in this case? If yes, you say a kernel with this patch
applied should let me import the pool without rollback?

The github issue is from 2022, I have my doubts that this is the same issue
we see. I rather expect some issues around the copy_file_range(2) related
code for ZFS which was re-enabled 20 days ago (maybe it is valid to remove
this assert, or maybe the block cloning part needs some tweak). CC Martin
for the block cloning part.

Bye,
Alexander.