[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Kernel panic: "panic: leaf should be empty"
Hi,
I'm having a problem with one of my servers lately. The machine crashes
at random times.
I've had the same panic several times. First my syslog will output
"vnode: table is full" and then the machine will crash. The output
below is from a crash at 1u30, just when the daily script was started.
So I think the problem is with the number of open files.
Would the problem be solved when changing kern.maxvnodes to a higher
number?
I already changed my apache configuration so it would take at least
half of the files it was before. (i checked it with fstat)
I'm running OpenBSD 3.4 (x86), i can't give you a `dmesg` yet because
it just crashed again and
its colocated. It crashed just after i updated to OpenBSD 3.5, which
was running fine, but when i left to the cinema and came back it was
down.
I'm not sure yet if the problem is still the same, but everything seems
the same. I can give more information(dmesg, current kern.maxvnodes,
same panic or not ...) tomorrow when i go to the data center.
I hope someone knows how to fix my problem. :(
may 4 01:30:05 sequel /bsd: vnode: table is full
panic: leaf should be empty
stopped at Debugger+0x4: movl %ebp,%esp
ddb> trace
Debugger(e8712e90, e8712eb4, e838e0c4, e85fcb4c, e8712ea0) at
Debugger+0x4
panic(d028ddc8,e8712ea0,e8712eb4,d15e2420,e838e0c4) at panic+0x83
lookup(e8712e90,d15e2400,400,e8712ea8,0) at lookup+0x29ej
namei(e8712e90,0,e8678b64,406b342b,0) at namei+0x347
sys_lstat(e8678b64,e8712f88,e8712f7c,d0241eab,230f5914) at
sys_lstat+0x4f
syscall() at syscall+0x171
--- syscall (number 190) ---
0x3116fbd:
Cheers,
Kenny Gryp
--
http://gryp.dakin.be