panic: ufs_rename: lost dir entry
Starting stack trace...
panic(ffffffff82583a2a) at panic+0x155 sys/kern/subr_prf.c:229
ufs_rename(ffff800029a25508) at ufs_rename+0x1649 sys/ufs/ufs/ufs_vnops.c:909
VOP_RENAME(fffffd807efd11b0,fffffd8063c23798,ffff800029a256d8,fffffd8076f6b7d0,fffffd8064bc6b20,ffff800029a25628) at VOP_RENAME+0xf0 sys/kern/vfs_vops.c:370
dorenameat(ffff8000216f0fc0,4,20000180,6,200001c0) at dorenameat+0x29c sys/kern/vfs_syscalls.c:3033
syscall(ffff800029a25870) at syscall+0x447 sys/arch/amd64/amd64/trap.c:585
Xsyscall() at Xsyscall+0x128
end of kernel
end trace frame: 0xf77e557ea00, count: 251
End of stack trace.
syncing disks...17 1  done

dump to dev 4,1 not possible
rebooting...
SeaBIOS (version 1.8.2-google)
Total RAM Size = 0x0000000080000000 = 2048 MiB
CPUs found: 2     Max CPUs supported: 2
SeaBIOS (version 1.8.2-google)
Machine UUID 7bbb59a4-3b4e-2ed3-58f8-154d5cc405f8
found virtio-scsi at 0:3
virtio-scsi vendor='Google' product='PersistentDisk' rev='1' type=0 removable=0
virtio-scsi blksize=512 sectors=4194304 = 2048 MiB
drive 0x000f24c0: PCHS=0/0/0 translation=lba LCHS=520/128/63 s=4194304
Sending Seabios boot VM event.
Booting from Hard Disk 0...
>> OpenBSD/amd64 BOOT 3.55
boot> set $lines = 0
set: syntax error
boot> set $maxwidth = 0
set: syntax error
boot> show panic
boot: illegal argument panic
boot> trace
boot> show registers
boot> show proc
boot> ps
boot> show all locks
boot> show malloc
boot> show all pools
boot> machine ddbcpu 0
machine: syntax error
boot> trace
boot> machine ddbcpu 1
machine: syntax error
boot> trace