panic: vop_generic_bad
op
Stopped at      db_ent
er+0x18:        addq    $
0x8,%rsp
    TID    PID    UID     P
RFLAGS     PFLAGS  CPU
  COMMAND
*219238  39389      0         0
x2          0    0  sy
z-executor.2
db_enter() at db_enter
+0x18
panic(ffffffff8255fb6b
) at panic+0x161 sys/kern/subr_prf.c:202
vop_generic_badop(ffff
80002b3b4ac8) at vop_g
eneric_badop+0x1b
VOP_STRATEGY(fffffd805
d3a7d38,fffffd805d5b46
c0) at VOP_STRATEGY+0x
9b
bwrite(fffffd805d5b46c
0) at bwrite+0x1e7 sys/kern/vfs_bio.c:763
VOP_BWRITE(fffffd805d5
b46c0) at VOP_BWRITE+0
x4a
ufs_mkdir(ffff80002b3b
4d60) at ufs_mkdir+0x6 sys/ufs/ufs/ufs_vnops.c:1134
b4
VOP_MKDIR(fffffd806905
f660,ffff80002b3b4ec0,
ffff80002b3b4ef0,ffff8
0002b3b4df0) at VOP_MK
DIR+0xbf
domkdirat(ffff80002167
8fd0,ffffff9c,7f7ffffd
50f0,1ff) at domkdirat
+0x121
syscall(ffff80002b3b50
70) at syscall+0x44e sys/arch/amd64/amd64/trap.c:585
Xsyscall() at Xsyscall
+0x128
end of kernel
end trace frame: 0x7f7
ffffd5160, count: 4
https://www.openbsd.or
g/ddb.html describes t
he minimum info requir
ed in bug
reports.  Insufficient
 info makes it difficu
lt to find and fix bug
s.