xfs-masters
[Top] [All Lists]

[Bug 976] xfs_repair v3.1.11 -- segfault in Phase 6 Badness key lookup (

To: xfs-masters@xxxxxxxxxxx
Subject: [Bug 976] xfs_repair v3.1.11 -- segfault in Phase 6 Badness key lookup (length) : get_inode_offset at incore.h:319
From: bugzilla-daemon@xxxxxxxxxxx
Date: Sun, 25 Aug 2013 17:21:54 +0000
Auto-submitted: auto-generated
Delivered-to: xfs-masters@xxxxxxxxxxx
In-reply-to: <bug-976-113@xxxxxxxxxxxxxxxx/bugzilla/>
References: <bug-976-113@xxxxxxxxxxxxxxxx/bugzilla/>
changed bug 976
What Removed Added
CC   sandeen-xfs@sandeen.net

Comment # 2 on bug 976 from
Can you please try the latest git tree?  I think this recent commit fixes it:

commit 3ac87fbf6ac29494dc46134323733551aac1737c
Author: Mark Tinguely <tinguely@sgi.com>
Date:   Fri Aug 16 18:12:43 2013 +0000

    xfsprogs: fix inode crash in xfs_repair

    Adding the lost+found in phase 6 could allocate an inode from
    a new inode chunk. Since this chunk was not around in phase 3
    when the inode chunks are verificated and added to the avl tree,
    the avl tree look up will return a NULL pointer. This results
    in a NULL defererence and segmentation fault.

    Add the newly created inode chunk as if found in the chunk
    verification phase.

    Signed-off-by: Mark Tinguely <tinguely@sgi.com>
    Reviewed-by: Rich Johnston <rjohnston@sgi.com>
    Signed-off-by: Rich Johnston <rjohnston@sgi.com>

quick-start:

# git clone git://oss.sgi.com/xfs/cmds/xfsprogs.git
# cd xfsprogs
# make
# repair/xfs_repair $DEVICE

-Eric


You are receiving this mail because:
  • You are the assignee for the bug.
<Prev in Thread] Current Thread [Next in Thread>
  • [Bug 976] xfs_repair v3.1.11 -- segfault in Phase 6 Badness key lookup (length) : get_inode_offset at incore.h:319, bugzilla-daemon <=