From nobody Thu Apr 30 18:12:46 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 4g62Mn69mqz6bygL for ; Thu, 30 Apr 2026 18:12:53 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Received: from smtp-42a9.mail.infomaniak.ch (smtp-42a9.mail.infomaniak.ch [84.16.66.169]) (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 "relay.mail.infomaniak.ch", Issuer "R12" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4g62Mm2Gg0z3wHG for ; Thu, 30 Apr 2026 18:12:52 +0000 (UTC) (envelope-from dumbbell@FreeBSD.org) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=freebsd.org (policy=none); spf=softfail (mx1.freebsd.org: 84.16.66.169 is neither permitted nor denied by domain of dumbbell@FreeBSD.org) smtp.mailfrom=dumbbell@FreeBSD.org Received: from smtp-4-0000.mail.infomaniak.ch (smtp-4-0000.mail.infomaniak.ch [10.7.10.107]) by smtp-4-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 4g62Mj5qjtzBY1 for ; Thu, 30 Apr 2026 20:12:49 +0200 (CEST) Received: from unknown by smtp-4-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4g62Mj387yzcK4 for ; Thu, 30 Apr 2026 20:12:49 +0200 (CEST) Message-ID: <07ab9cba-8089-4fd3-9bc7-31bbdbf0bffe@FreeBSD.org> Date: Thu, 30 Apr 2026 20:12:46 +0200 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 User-Agent: Mozilla Thunderbird Subject: Re: openzfs panic: VERIFY3U(offset, <, dn->dn_datablksz) failed To: freebsd-current@freebsd.org References: <34C033D4-AC92-4E11-A130-AFFBAB6CCB45@FreeBSD.org> Content-Language: en-US, fr From: =?UTF-8?Q?Jean-S=C3=A9bastien_P=C3=A9dron?= Organization: The FreeBSD Project In-Reply-To: <34C033D4-AC92-4E11-A130-AFFBAB6CCB45@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Infomaniak-Routing: alpha X-Spamd-Result: default: False [-0.23 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; NEURAL_SPAM_LONG(0.99)[0.988]; R_MIXED_CHARSET(0.83)[subject]; NEURAL_HAM_SHORT(-0.56)[-0.558]; RWL_MAILSPIKE_EXCELLENT(-0.40)[84.16.66.169:from]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : No valid SPF, No valid DKIM,none]; RCVD_IN_DNSWL_LOW(-0.10)[84.16.66.169:from]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; HAS_ORG_HEADER(0.00)[]; FREEFALL_USER(0.00)[dumbbell]; ASN(0.00)[asn:29222, ipnet:84.16.64.0/19, country:CH]; RCVD_VIA_SMTP_AUTH(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_TWO(0.00)[2]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; R_DKIM_NA(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_ONE(0.00)[1] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4g62Mm2Gg0z3wHG On 25/04/2026 10:24, Kristof Provost wrote: > On 24 Apr 2026, at 14:18, Alexander Leidinger wrote: > 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 = > > 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. I get it while working on RabbitMQ as well, 100% reproducible. I shared what I think I understand of the problem on the pull request that added POSIX_FADV_DONTNEED support: https://github.com/openzfs/zfs/pull/18399 However, the patch I drafted, even though it does not cause the panic anymore, is incorrect as I misunderstood that code. -- Jean-Sébastien Pédron The FreeBSD Project