Re: CURRENT: Panic VERIFY(!zil_replaying(zilog, tx)) failed (and crashing)

Am Sun, 9 Apr 2023 14:37:03 +0200
Mateusz Guzik <mjguzik@gmail.com> schrieb:

> On 4/9/23, FreeBSD User <freebsd@walstatt-de.de> wrote:
> > Today, after upgrading to FreeBSD 14.0-CURRENT #8 main-n262052-0d4038e3012b:
> > Sun Apr  9
> > 12:01:02 CEST 2023  amd64, AND upgrading ZPOOLs via
> >
> > zpool upgrade POOLNAME
> >
> > some boxes keep crashing when starting compiler runs (the trigger is
> > different on boxes).
> >
> > ZFS module is statically compiled into the kernel (if this is of
> > importance)
> >
> > Last known good was:
> >
> > [...]
> > Apr  9 07:10:04 <0.2> thor kernel: FreeBSD 14.0-CURRENT #7
> > main-n262051-75379ea2e461: Sun Apr
> > 9 00:12:57 CEST 2023 Apr  9 07:10:04 <0.2> thor kernel:
> > root@thor:/usr/obj/usr/src/amd64.amd64/sys/THOR amd64 Apr  9 07:10:04 <0.2>
> > thor kernel:
> > FreeBSD clang version 15.0.7 (https://github.com/llvm/llvm-project.git
> > llvmorg-15.0.7-0-g8dfdcc7b7bf6) Apr  9 07:10:04 <0.2> thor kernel:
> > VT(efifb): resolution
> > 2560x1440 Apr  9 07:10:04 <0.2> thor kernel: module zfsctrl already
> > present!
> > [...]
> >
> > The file /var/crash/info.X
> >
> > contains:
> >
> > [...]
> >
> > root@thor:/var/crash # more info.2
> > Dump header from device: /dev/gpt/swap
> >   Architecture: amd64
> >   Architecture Version: 2
> >   Dump Length: 1095192576
> >   Blocksize: 512
> >   Compression: none
> >   Dumptime: 2023-04-09 11:43:41 +0000
> >   Hostname: thor.local
> >   Magic: FreeBSD Kernel Dump
> >   Version String: FreeBSD 14.0-CURRENT #8 main-n262052-0d4038e3012b: Sun Apr
> >  9 12:01:02 CEST
> > 2023
> >     root@thor:/usr/obj/usr/src/amd64.amd64/sys/THOR
> >   Panic String: VERIFY(!zil_replaying(zilog, tx)) failed
> >
> >   Dump Parity: 2961465682
> >   Bounds: 2
> >   Dump Status: good
> >
> > Until reconfigured for more debug stuff I do not have more to present.
> >
> > I rememeber now really scraed that there was a HEADSUP in the list regarding
> > some serious ZFS
> > problems - I didn't find it right now.
> >
> > Thanks in advance,
> >  
> 
> That's fallout from the new block cloning feature, adding the author
> 

Thanks.

As of this moment, all systems with the newest kernel and the new ZFS option enabled, crash -
the reason is mostly in  different ZFS datasets. I guess there is no way back once this faulty
option is enabled?

Regards,

oh

-- 
O. Hartmann