This is a discussion on panic: bad dir within the mailing.openbsd.tech forums, part of the OpenBSD category; --> I can reliably reproduce the following panic. That's on a net4801 with 4.0 and the following disk structure: - ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I can reliably reproduce the following panic. That's on a net4801 with 4.0 and the following disk structure: - rd0 root - svnd disk mounted on top - ramdisk mounted on top I can provide more details if someone is interested... Clues/Workarounds welcomes Cedric First bad /mnt/fw: bad dir ino 2 at offset 0: mangled entry panic: bad dir Stopped at Debugger+0x4: leave RUN AT LEAST 'trace' AND 'ps' AND INCLUDE OUTPUT WHEN REPORTING THIS PANIC! DO NOT EVEN BOTHER REPORTING THIS WITHOUT INCLUDING THAT INFORMATION! ddb> trace Debugger(d0f49200,d2f3e7e4,d6b4bd34,d03cd474,d05ec 55b) at Debugger+0x4 panic(d05ec55b,0,d6b4bdb0,d03cccd4,d2f3e7e4) at panic+0x76 ufs_dirbad(d2f3e7e4,0,d05ec538,d2f3e7e4,c044) at ufs_dirbad+0x3a ufs_lookup(d6b4bdbc,d068d340,d2f3c30c,d6b4be7c,d6b 4be90) at ufs_lookup+0x3f0 VOP_LOOKUP(d2f3c30c,d6b4be7c,d6b4be90) at VOP_LOOKUP+0x2e lookup(d6b4be6c,d2fa8ca8,3,d2faeb90,0) at lookup+0x278 namei(d6b4be6c,85264f88,0,0,d2fa3138) at namei+0x1ce sys_stat(d2fa8ca8,d6b4bf74,d6b4bf68,0,14) at sys_stat+0x4a syscall() at syscall+0x205 --- syscall (number 291) --- 0x1c13eecd: ddb> ps PID PPID PGRP UID S FLAGS WAIT COMMAND 20112 1 20112 0 3 0x84 select bsshd 17250 1 17250 77 3 0x184 poll dhclient 17633 1 17691 0 3 0x86 poll dhclient *17691 1 17691 0 7 0x4006 sh 9 0 0 0 3 0x100204 crypto_wa crypto 8 0 0 0 3 0x100204 aiodoned aiodoned 7 0 0 0 3 0x100204 syncer update 6 0 0 0 3 0x100204 cleaner cleaner 5 0 0 0 3 0x100204 reaper reaper 4 0 0 0 3 0x100204 pgdaemon pagedaemon 3 0 0 0 3 0x100204 pftm pfpurge 2 0 0 0 3 0x100204 kmalloc kmthread 1 0 1 0 3 0x4084 wait init 0 -1 0 0 3 0x80204 scheduler swapper ddb> |