On Mon, 2000-09-04 08:57:09 +1100, Keith Owens wrote:
> klogd has got in first and stamped on the trace, got it wrong
> and left no useful trace data for ksymoops.
Geez. I noticed it too late. Meanwhile I hit another nice one
while trying to reproduce the vnode-crash. The kernel crashed so
badly that syslogd/klogd didn't have time to log the oops---no
console copy either since a reboot occured. What I could recover
from the filesystem follows:
Sep 6 19:17:56 pcrd18 kernel: XFS assertion failed:xfs_bmbt_get_startoff(r1) +
xfs_bmbt_get_blockcount(r1) <=
xfs_bmbt_get_startoff(r2), file: xfs_btree.c, line: 300
Sep 6 19:17:57 pcrd18 kernel: kernel BUG at xfs_debug.c:50!
Sep 6 19:17:57 pcrd18 kernel: invalid operand: 0000
Sep 6 19:17:57 pcrd18 kernel: CPU: 1
...and that's it. After reboot, the kernel was able to mount the
(obviously) damaged XFS filesystem, but running xfs_repair dumped
core (backtrace attached).
Peter
--
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen Péter / \ / \ Peter.Kelemen@xxxxxxx
.+' `+...+' `+...+' `+...+' `+...+'
gdb.xfs_repair
Description: Text document
|