NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/54647: panic: ffs_newvnode: dup alloc ino=2782620

>Number:         54647
>Category:       kern
>Synopsis:       panic: ffs_newvnode: dup alloc ino=2782620
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 25 04:50:00 +0000 2019
>Originator:     Lawrence D'Anna
>Release:        8.1_STABLE
NetBSD localhost 8.1_STABLE NetBSD 8.1_STABLE (GENERIC) #0: Thu Oct 17 18:41:27 UTC 2019 amd64     

netbsd# panic: ffs_newvnode: dup alloc ino=2782620 on /data: mode a1ed/a1ed gen 3835531f/3835531f size 0 blocks 8
cpu0: Begin traceback...
vpanic() at netbsd:vpanic+0x15d
snprintf() at netbsd:snprintf
ffs_newvnode() at netbsd:ffs_newvnode+0x530
vcache_new() at netbsd:vcache_new+0x95
ufs_makeinode() at netbsd:ufs_makeinode+0x38
ufs_symlink() at netbsd:ufs_symlink+0x3a
VOP_SYMLINK() at netbsd:VOP_SYMLINK+0x58
do_sys_symlinkat.isra.4() at netbsd:do_sys_symlinkat.isra.4+0x219
syscall() at netbsd:syscall+0x1ec
--- syscall (number 57) ---
cpu0: End traceback...

I've got a VM I was using to build LLDB that panics like that every time I start the build back up again.

Home | Main Index | Thread Index | Old Index