Skip site navigation (1)Skip section navigation (2) 
Date:      Sat, 25 Apr 2026 10:24:27 +0200
From:      Kristof Provost <kp@FreeBSD.org>
To:        Alexander Leidinger <Alexander@Leidinger.net>
Cc:        Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: openzfs panic: VERIFY3U(offset, <, dn->dn_datablksz) failed
Message-ID:  <34C033D4-AC92-4E11-A130-AFFBAB6CCB45@FreeBSD.org>
In-Reply-To: <d41fa969c39062e325e1991616708a6d@Leidinger.net>
index | next in thread | previous in thread | raw e-mail 

[-- Attachment #1 --]
On 24 Apr 2026, at 14:18, Alexander Leidinger wrote:
> Hi,
>
> recent current (last commit 2026-04-23-222413).
>
> short:
> #3  0xffffffff805502f7 in vpanic (
>     fmt=0xffffffff82556d5d "VERIFY3U(offset, <, dn->dn_datablksz) 
> failed (%llu < %llu)\n", ap=ap@entry=0xfffffe0228f57c70)
>     at /space/system/usr_src/sys/kern/kern_shutdown.c:974
>         buf = "VERIFY3U(offset, <, dn->dn_datablksz) failed 
> (9223372036854775807 < 24576)\n", '\000' <repeats 180 times>
>         __pc = 0x0
>         __pc = 0x0
>         __pc = 0x0
>         other_cpus = {__bits = {16777213, 0 <repeats 15 times>}}
>         td = 0xfffff80741b6e780
>         bootopt = <unavailable>
>         newpanic = <optimized out>
>
> See attachment for a full backtrace. vmcore available.
>
> I can trigger this with a postgresql18 initdb call (I tried an upgrade 
> from postgresql 17 to 18, copy & paste of the UPDATING entry for the 
> initdb call).
>
> No zpool status issues, I started a scrub to see if it detects some 
> issues. This is a 5T pool on spinning drives, so it may take a moment.
>
I’m seeing the same panic (somewhat regularly, without obvious 
trigger), so I’m fairly confident it’s not some obscure corruption 
in your pool.

Best regards,
Kristof
[-- Attachment #2 --]
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">On 24 Apr 2026, at 14:18, Alexander Leidinger wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #136BCE; color: #136BCE;">
<p dir="auto">Hi,</p>
<p dir="auto">recent current (last commit 2026-04-23-222413).</p>
<p dir="auto">short:<br>
#3  0xffffffff805502f7 in vpanic (<br>
fmt=0xffffffff82556d5d &quot;VERIFY3U(offset, &lt;, dn-&gt;dn_datablksz) failed (%llu &lt; %llu)\n&quot;, ap=ap@entry=0xfffffe0228f57c70)<br>
at /space/system/usr_src/sys/kern/kern_shutdown.c:974<br>
buf = &quot;VERIFY3U(offset, &lt;, dn-&gt;dn_datablksz) failed (9223372036854775807 &lt; 24576)\n&quot;, '\000' &lt;repeats 180 times&gt;<br>
__pc = 0x0<br>
__pc = 0x0<br>
__pc = 0x0<br>
other_cpus = {__bits = {16777213, 0 &lt;repeats 15 times&gt;}}<br>
td = 0xfffff80741b6e780<br>
bootopt = &lt;unavailable&gt;<br>
newpanic = &lt;optimized out&gt;</p>
<p dir="auto">See attachment for a full backtrace. vmcore available.</p>
<p dir="auto">I can trigger this with a postgresql18 initdb call (I tried an upgrade from postgresql 17 to 18, copy &amp; paste of the UPDATING entry for the initdb call).</p>
<p dir="auto">No zpool status issues, I started a scrub to see if it detects some issues. This is a 5T pool on spinning drives, so it may take a moment.</p>
</blockquote>
<p dir="auto">I’m seeing the same panic (somewhat regularly, without obvious trigger), so I’m fairly confident it’s not some obscure corruption in your pool.</p>
<p dir="auto">Best regards,<br>
Kristof</p>

</div>
</div>
</body>

</html>
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34C033D4-AC92-4E11-A130-AFFBAB6CCB45>