From nobody Mon Jan 27 17:38:03 2025 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 4YhbHC32f9z5m0yb for ; Mon, 27 Jan 2025 17:38:15 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Received: from cm0.netlabit.sk (mailhost.netlabit.sk [84.245.65.72]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4YhbH91vtZz3gvw for ; Mon, 27 Jan 2025 17:38:12 +0000 (UTC) (envelope-from freebsd-current@dino.sk) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of freebsd-current@dino.sk designates 84.245.65.72 as permitted sender) smtp.mailfrom=freebsd-current@dino.sk; dmarc=none Received: from dino.sk ([84.245.95.254]) (AUTH: LOGIN milan, TLS: TLSv1.3,256bits,TLS_AES_256_GCM_SHA384) by cm0.netlabit.sk with ESMTPSA id 00000000021C1AE8.000000006797C47D.00004A67; Mon, 27 Jan 2025 18:38:05 +0100 Date: Mon, 27 Jan 2025 18:38:03 +0100 From: Milan Obuch To: freebsd-current@freebsd.org Subject: Re: UFS bad inode, mangled entry on Alder Lake-N(100) Message-ID: <20250127183803.23683162.25648751.59233766@dino.sk> In-Reply-To: References: X-Mailer: Claws Mail 3.21.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.3) 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: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-3.30 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:5578, ipnet:84.245.64.0/18, country:SK]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[dino.sk]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YhbH91vtZz3gvw On Mon, 27 Jan 2025 12:10:43 -0500 Ian FREISLICH wrote: > I recently bought one of those mini-pc firewall devices (Topton 12th > gen N100 with 4x I226-V, 2x X520) and couldn't get it to install pkg > or buildkernel without getting a slew of these messages, inode number > changing and a panic shortly thereafter. > > kernel: /: bad dir ino 4567815 at offset 0: mangled entry > > I tried the FreeBSD-15.0-CURRENT-amd64-20250124 snapshot and > 14.2-RELEASE, both with and without journal, trim and softupdates in > every permitted permutation without success. The system has an NVME, > but I experience the same problem with the install on a microsd and > different known good NVME drive. Each time I had to reinstall because > the filesystem was so corrupted it wouldn't boot after a fsck. > > The system is now running fine with ZFS so I'm wondering if it's > silently corrupting the ZFS or if there's a bug in UFS2 that's > tickled by this CPU. I'll provide any debugging required. Just a "me too" message - I did test another device with the same CPU, mine is SZBOX. Only with 14.2-RELEASE, but I tested with both NVMe and M.2 SATA devices, both direct in miniPC and externally via USB-NVMe and USB-M.2 SATA converters. System installation went flawless, however, just building ports-mgmt/pkg port was enough to start generate mangled entry messages as you wrote. To me it look like there is some bug in UFS code when used with this CPU, I have no idea how such a bug could not manifest itself on another platform - I was convinced UFS code is hardware independent, this is really strange. I did not test with ZFS yet, I plan to do it. So, if I can test something, patch, different setup, provide some debugging, count me in. Regards, Milan