Re: Repeated ffs_newvnode panic (dup alloc) on one inode

On Wednesday 10 Dec 2025, at 13:28, Edgar Fuß wrote:
> > After some lengthy 'find -inum' I did confirm that the inode NNN
> > didn't exist on the filesystem.
> At least not linked to a directory.
>
> What does fsdb say?

I just discovered that command (which would have helped during the
panics).

It seems that the inode is clean on disk ...

# fsdb -n -N /dev/rraid0a
** /dev/rraid0a (NO WRITE)
** File system is journaled; replaying journal
CANNOT REPLAY JOURNAL IN -n MODE; continuing anyway
Editing file system `/dev/rraid0a'
Last Mounted on /home
current inode: directory
I=2 MODE=40755 SIZE=512 EXTSIZE=0
            MTIME=Sep 20 21:45:03 2019 [228034095 nsec]
            CTIME=Sep 20 21:45:03 2019 [228035157 nsec]
            ATIME=Oct 18 03:25:59 2024 [642553311 nsec]
        BIRTHTIME=Jan  8 13:20:53 2011 [725874000 nsec]
OWNER=root GRP=wheel LINKCNT=16 FLAGS=0x0 BLKCNT=0x8 GEN=0x2db73e5e
fsdb (inum: 2)> inode 5242183
current inode 5242183: unallocated inode
fsdb (inum: 5242183)>

Btw, the exact panic message was:
Dec  9 20:56:44 cactus savecore: reboot after panic: [ 668223.3395537] panic: ffs_newvnode: dup alloc ino=5242183 on /home: mode 142/142 gen 0/0 size 0 blocks 0

I also had one back on Dec. 2 which happened while I was not present
and the system rebooted just fine by itsel:
Dec  2 03:14:37 cactus savecore: reboot after panic: [ 2445708.0246909] panic: f
fs_newvnode: dup alloc ino=5242183 on /home: mode 142/142 gen 0/0 size 0 blocks
0