kern/58009: ffs_newvnode panic while untarring comp.tar.xz

[nia%mailfence.com@localhost]

>Number:         58009
>Category:       kern
>Synopsis:       ffs_newvnode panic while untarring comp.tar.xz
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 08 08:40:00 +0000 2024
>Originator:     nia
>Release:        10.0_RC5
>Organization:
The NetBSD Foundation
>Environment:
NetBSD amnesia 10.0_RC5 NetBSD 10.0_RC5 (GENERIC) #0: Tue Feb 27 05:27:39 UTC 2024  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/amd64/compile/GENERIC amd6
>Description:
file system was mounted with options rw,log,noatime

/encrypt: replaying log to disk
panic: ffs_newvnode: dup alloc ino=3623063 on /: mode 2005/2005 gen 0/0 size 0 blocks 0
cpu1: Begin traceback...
[ c() at netbsd:panic+0x3c
[ 137.6268827] ffs_newvnode() at netbsd:ffs_newvnode+0x572
vcache_new() at netbsd:vcache_new+0x97
ufs_makeinode() at netbsd:ufs_makeinode+0x3c
ufs_create() at netbsd:ufs_create+0x36
VOP_CREATE() at netbsd:VOP_CREATE+0x43

syscall() at netbsd:syscall+0x1fc
--- syscall (number 5) ---
netbsd:syscall+0x1fc:
cpu1: End traceback...

dumping to dev 168,2 (offset=1767, size=2059555):

>How-To-Repeat:

>Fix:
deleting /usr/share/man before untarring seemed to resolve ffs's problems