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.
Ian
- UFS bad inode, mangled entry on Alder Lake-N(100) Ian FREISLICH
- Re: UFS bad inode, mangled entry on Alder Lake-N(10... Milan Obuch
- Re: UFS bad inode, mangled entry on Alder Lake-... Patrick M. Hausen
- Re: UFS bad inode, mangled entry on Alder L... Ian FREISLICH
- Re: UFS bad inode, mangled entry on Alder L... Ian FREISLICH
- Re: UFS bad inode, mangled entry on Alder Lake-N(10... Yamagi
- Re: UFS bad inode, mangled entry on Alder Lake-... Milan Obuch
- Re: UFS bad inode, mangled entry on Alder L... Ian FREISLICH