[Top] [All Lists]

xfs_repair dumps core on damaged filesystem (was: Re: XFS assertion fail

To: Keith Owens <kaos@xxxxxxxxxxxxxxxxx>
Subject: xfs_repair dumps core on damaged filesystem (was: Re: XFS assertion failed: vp->v_bh.bh_first != NULL)
From: Peter.Kelemen@xxxxxxx
Date: Wed, 6 Sep 2000 22:47:53 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <17574.968018229@xxxxxxxxxxxx>; from kaos@xxxxxxxxxxxxxxxxx on Mon, Sep 04, 2000 at 08:57:09AM +1100
Organization: CERN European Laboratory for Particle Physics, Switzerland
References: <20000903211728.C3797@xxxxxxxxxxxxxx> <17574.968018229@xxxxxxxxxxxx>
Reply-to: Peter.Kelemen@xxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
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).


    .+'''+.         .+'''+.         .+'''+.         .+'''+.         .+''
 Kelemen Péter     /       \       /       \     Peter.Kelemen@xxxxxxx
.+'         `+...+'         `+...+'         `+...+'         `+...+'

Attachment: gdb.xfs_repair
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>