From nobody Tue Apr 7 18:21:55 2026 X-Original-To: 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 4fqvg611sWz6Yhgc for ; Tue, 07 Apr 2026 18:22:10 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail3.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 4fqvg45k2Hz3RXX for ; Tue, 07 Apr 2026 18:22:08 +0000 (UTC) (envelope-from janm@transactionware.com) Authentication-Results: mx1.freebsd.org; none Received: (qmail 11422 invoked by uid 907); 7 Apr 2026 18:22:07 -0000 Received: from ip-109-41-48-64.web.vodafone.de (HELO smtpclient.apple) (109.41.48.64) (smtp-auth username janm, mechanism plain) by mail3.transactionware.com (qpsmtpd/0.84) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Wed, 08 Apr 2026 04:22:07 +1000 Content-Type: text/plain; charset=utf-8 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 (Mac OS X Mail 16.0 \(3864.500.181\)) Subject: Re: Panic: cache_vop_rename: lingering negative entry From: Jan Martin Mikkelsen In-Reply-To: <9c-3l5dvbjve6vGZbCL2k2grqQoncLsoUv3HI55UrDfP0MPUyMqrdFP6eUe8TFA-lkzDqZqE13HtwfhvLml6OP9fl3CIaptORG-SjYWrusU=@proton.me> Date: Tue, 7 Apr 2026 20:21:55 +0200 Cc: current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8B1B313C-BF0E-45F4-9832-BF009A53DD32@transactionware.com> References: <2016260A-5C07-45EE-87CA-73918BA16E83@transactionware.com> <9c-3l5dvbjve6vGZbCL2k2grqQoncLsoUv3HI55UrDfP0MPUyMqrdFP6eUe8TFA-lkzDqZqE13HtwfhvLml6OP9fl3CIaptORG-SjYWrusU=@proton.me> To: Minsoo Choo X-Mailer: Apple Mail (2.3864.500.181) X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:17559, ipnet:203.14.245.0/24, country:AU] X-Rspamd-Queue-Id: 4fqvg45k2Hz3RXX X-Spamd-Bar: ---- On 7 Apr 2026, at 17:25, Minsoo Choo wrote: >=20 > On Wednesday, April 8th, 2026 at 12:03 AM, Jan Martin Mikkelsen = wrote: >=20 >> Hi, >>=20 >> I am consistently getting the panic below while building = lang/perl5.42. This is the command from the perl build that triggers the = panic: >>=20 >> /usr/bin/strip = /ports-work/usr/ports/lang/perl5.42/work/stage/usr/local/bin/perl5.42.0 >>=20 >> CURRENT on aarch64, with a kernel from last week, also with a later = one from the weekend. A kernel from mid-January worked fine. >>=20 >> I can reproduce on demand, no parallelism in the build required. >>=20 >> Does this look familiar to anyone? >>=20 >> panic: cache_vop_rename: lingering negative entry >> cpuid =3D 4 >> time =3D 1775410763 >> KDB: stack backtrace: >> db_trace_self() at db_trace_self >> db_trace_self_wrapper() at db_trace_self_wrapper+0x38 >> vpanic() at vpanic+0x1a0 >> panic() at panic+0x48 >> cache_vop_rename() at cache_vop_rename+0xb0 >> zfs_do_rename() at zfs_do_rename+0xafc >> zfs_freebsd_rename() at zfs_freebsd_rename+0x5c >> VOP_RENAME_APV() at VOP_RENAME_APV+0x44 >> kern_renameat () at kern_renameat+0x574 >> do_el0_sync() at do_el0_sync+0x5f8 >> handle_el0_sync() at handle_el0_sync+0x4c >> --- exception, esr 0x56000000 >> KDB: enter: panic >> [ thread pid 81230 tid 101738 ] >> Stopped at kdb_enter+0x48: str xzr, [x19, #3072] >>=20 >> Regards, >>=20 >> Jan M. >>=20 >>=20 >>=20 >=20 > The panic message says the kernel panic is triggered by zfs. KASSERT = at = https://github.com/freebsd/freebsd-src/blob/cff675e83cdb6c9027e94df9d01043= 9e42e27dee/sys/kern/vfs_cache.c#L3093 triggered the panic, but HOW (not = WHERE) the panic occurred can only be determined by observing the crash = dump. >=20 > I assume race conditions happened during the I/O heavy workload, but = at the same time you said no parallelism in build required. To make = sure, could you run zfs scrub on the file system? The filesystems were scrubbed multiple times while I was investigating = this problem. I just re-ran the test after a scrub, and yes, it panics. I don=E2=80=99t think there is a lot of I/O involved. Reboot, run = =E2=80=9Cmake build=E2=80=9D on lang/perl5.42, then run =E2=80=9Cmake = install=E2=80=9D and observe the panic. That=E2=80=99s on ZFS, tmpfs/UFS = are different. (see other email.) Regards, Jan M.=