From nobody Sat Apr 25 08:24:27 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4g2jYC65SLz6b44m for ; Sat, 25 Apr 2026 08:24:31 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4g2jYC5F3rz3gQS; Sat, 25 Apr 2026 08:24:31 +0000 (UTC) (envelope-from kp@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1777105471; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qdu0gT3i7InaC97pn1m9nrkfw6ueEkIdlaabfF9X3r8=; b=AxJGGobbc1K3NNUHhcaWXaBZwAfgmY/vLCjuLxfMbX6jfApGdhSokquKyieiRmBK6itlHV MFg1lP6QIrVCvcS4ruAAxlsEF0BqXlGR39NPOrjshH/PKISZvAU+ZgueuuKsUxrlgGpnzp xQkYzJ/sX4XVnV+wWqRVsBjhrNIePJ1P7jMLiRyLP1fbCG1yyualTmG5hFECIiP7wKUKOF Zql6/FSP2TBfI8xHukXySQsTAhYTtjaHfUIq7liTWT26CcgaTS2g1jY9W6g1fXYgPWqdzw Dx0m0U9mWd2Joq174BQvXvcIe2TqmEY/P1/fLE422yzv0ZZ0I8Gki9O8orluGw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1777105471; a=rsa-sha256; cv=none; b=Uf/sl86TfUZArmeBjEbfH7F7XVdEbkFquI35uJZl/RkgFUYurRgp0vYS4crhR4Nn2nnGe4 Q7KAmmCgJGho+qWoqLRRIbmqqw0PRi+ulVVCnkmrMWekXfSt1xGK8rTXTPhUZ3w8Sd7qmx dOJAUeV+m8gEB4ctymKX70Tnlwrq8yakJcHUxz6AK5ropzF7FPdbtH++Zcap6ucMdP837Z k5GVQVbDL74b367nFau6bUid+AUW8M+G8qYJWWNxZu6aSCP2qbQ9++p3jAzv88b/u3Xhpx QNmf7dvjBJgmz/q75hDz16T+n0oOZSlbV2MPgJLTn0/CTx+bwizgHrcJDI1gIg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1777105471; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qdu0gT3i7InaC97pn1m9nrkfw6ueEkIdlaabfF9X3r8=; b=JN39sme7hpq2WqOiMDIbP3CKSCtNF+fYGhR5MHH79DPUhjkczDD/r1FYmIOwDu8S/GDKiB OyOFbLs0mqesY5f7brQrEcci1181loDI/J41FEuEjcOBvwkJm7+VVh06Uq+REGelcMWo7d rRnqrWLHzW4Q8+jN9btr2uNNwpr4uktI5u/fkud1aEV71X6wAdUfv59loExzlPBvCYB421 Bpg7jJYlUlzWKH0wuPOwVWjlcO9+ieRvZxZBMjBoUhXGMEJ0QsPXUlLaMTawcaAto+1OV8 HWZQOrlWLxDAK+AcRhzyqnJOcgx6pDITFYYXWUox1nP2i6VKqXYb90bqMtluIQ== Received: from venus.codepro.be (venus.codepro.be [5.9.86.228]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.codepro.be", Issuer "R12" (not verified)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id 4g2jYC3n2fzq4c; Sat, 25 Apr 2026 08:24:31 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 43926548CE; Sat, 25 Apr 2026 10:24:28 +0200 (CEST) From: Kristof Provost To: Alexander Leidinger Cc: Current FreeBSD Subject: Re: openzfs panic: VERIFY3U(offset, <, dn->dn_datablksz) failed Date: Sat, 25 Apr 2026 10:24:27 +0200 X-Mailer: MailMate (2.0r6272) Message-ID: <34C033D4-AC92-4E11-A130-AFFBAB6CCB45@FreeBSD.org> In-Reply-To: References: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_MailMate_630F8CCD-1B61-4133-8D44-48B0A3EA3BD1_=" Content-Transfer-Encoding: 8bit --=_MailMate_630F8CCD-1B61-4133-8D44-48B0A3EA3BD1_= Content-Type: text/plain; charset=UTF-8; format=flowed; markup=markdown Content-Transfer-Encoding: 8bit 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' > __pc = 0x0 > __pc = 0x0 > __pc = 0x0 > other_cpus = {__bits = {16777213, 0 }} > td = 0xfffff80741b6e780 > bootopt = > newpanic = > > 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 --=_MailMate_630F8CCD-1B61-4133-8D44-48B0A3EA3BD1_= Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

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=3D0xffffffff82556d5d "VERIFY3U(offset, <, dn->dn_datablksz= ) failed (%llu < %llu)\n", ap=3Dap@entry=3D0xfffffe0228f57c70) at /space/system/usr_src/sys/kern/kern_shutdown.c:974
buf =3D "VERIFY3U(offset, <, dn->dn_datablksz) failed (9223372= 036854775807 < 24576)\n", '\000' <repeats 180 times>
__pc =3D 0x0
__pc =3D 0x0
__pc =3D 0x0
other_cpus =3D {__bits =3D {16777213, 0 <repeats 15 times>}}
td =3D 0xfffff80741b6e780
bootopt =3D <unavailable>
newpanic =3D <optimized out>

See attachment for a full backtrace. vmcore available.

I can trigger this with a postgresql18 initdb call (I tri= ed 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 de= tects some issues. This is a 5T pool on spinning drives, so it may take a= moment.

I=E2=80=99m seeing the same panic (somewhat regularly, wi= thout obvious trigger), so I=E2=80=99m fairly confident it=E2=80=99s not = some obscure corruption in your pool.

Best regards,
Kristof

--=_MailMate_630F8CCD-1B61-4133-8D44-48B0A3EA3BD1_=--