All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Yves Brueckner <jyb@gmx.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair segfaulting in phase 3
Date: Wed, 04 Sep 2013 08:39:47 -0500	[thread overview]
Message-ID: <52273823.6050704@sandeen.net> (raw)
In-Reply-To: <trinity-9e6d7620-812f-48a7-9a7e-3098368ff59a-1376307533158@3capp-gmx-bs36>

On 8/12/13 6:38 AM, Jan Yves Brueckner wrote:
> Hi there,
> 
> as in previous posts we've got a problem in repair/dir2.c after a
> xfs_repair -L -m 60000 segfaulting reproducibly at the very same
> point of recovery;
> 
> I did the initial repair with debianish 2.9.8 (some patches applied);
> then upgrading to latest stable 3.1.11 where the problem persists.
> 
> 3.1.11 when compiled w/o optimization and run with gdb however
> segfaulted in libpthread so I repeated with an -O0 of 2.9.8 to get
> the debugging information:
> 

Jan - 3 bugfixes into this, and I can get repair to complete w/o
a segv.  However, the fs is still not fully repaired.
Nor is it fully repaired after the 2nd pass, etc etc.  :(

So you may have contributed a bit to xfs_repair stability
by uncovering this, but I'm not sure I will be able to contribute
to recovery of your (apparently _severely_ damaged) filesystem.

:(

-Eric

> corrupt block 35 in directory inode 39869938
> 
> will junk block
> 
> corrupt block 51 in directory inode 39869938
> 
> will junk block
> 
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 
> [Switching to Thread 0x7fcd982ae730 (LWP 19563)]
> 
> 0x0000000000419428 in verify_dir2_path (mp=0x7ffff8381580,
> cursor=0x7ffff8380f10, p_level=0) at dir2.c:619
> 
> 619             node = cursor->level[this_level].bp->data;
> 
> (gdb) info locals
> 
> node = (xfs_da_intnode_t *) 0x7ffff8380e94
> 
> newnode = (xfs_da_intnode_t *) 0x52202867f8380de0
> 
> dabno = 0
> 
> bp = (xfs_dabuf_t *) 0x80000200000001
> 
> bad = -474527744
> 
> entry = 0
> 
> this_level = 1
> 
> bmp = (bmap_ext_t *) 0x1
> 
> nex = 134250496
> 
> lbmp = {startoff = 8459390528, startblock = 72058695280238674,
> blockcount = 140737357811264, flag = 4309438}
> 
> __PRETTY_FUNCTION__ = "verify_dir2_path"
> 
> (gdb)
> 
> 
> 
> (gdb) bt
> 
> #0  0x0000000000419428 in verify_dir2_path (mp=0x7ffff8381580,
> cursor=0x7ffff8380f10, p_level=0) at dir2.c:619
> 
> #1  0x000000000041c441 in process_leaf_level_dir2 (mp=0x7ffff8381580,
> da_cursor=0x7ffff8380f10, repair=0x7ffff8381134)
> 
> at dir2.c:1899
> 
> #2  0x000000000041c61e in process_node_dir2 (mp=0x7ffff8381580,
> ino=39869938, dip=0x7fc9e2b38000, blkmap=0x7fca249ffd40,
> 
> repair=0x7ffff8381134) at dir2.c:1979
> 
> #3  0x000000000041c8cf in process_leaf_node_dir2 (mp=0x7ffff8381580,
> ino=39869938, dip=0x7fc9e2b38000, ino_discovery=1,
> 
> dirname=0x4911f6 "", parent=0x7ffff8381398, blkmap=0x7fca249ffd40,
> dot=0x7ffff838113c, dotdot=0x7ffff8381138,
> 
> repair=0x7ffff8381134, isnode=1) at dir2.c:2059
> 
> #4  0x000000000041cb33 in process_dir2 (mp=0x7ffff8381580,
> ino=39869938, dip=0x7fc9e2b38000, ino_discovery=1,
> 
> dino_dirty=0x7ffff8381390, dirname=0x4911f6 "",
> parent=0x7ffff8381398, blkmap=0x7fca249ffd40) at dir2.c:2113
> 
> #5  0x00000000004127ac in process_dinode_int (mp=0x7ffff8381580,
> dino=0x7fc9e2b38000, agno=0, ino=39869938, was_free=0,
> 
> dirty=0x7ffff8381390, cleared=0x7ffff838138c, used=0x7ffff8381394,
> verify_mode=0, uncertain=0, ino_discovery=1,
> 
> check_dups=0, extra_attr_check=1, isa_dir=0x7ffff8381388,
> parent=0x7ffff8381398) at dinode.c:2783
> 
> #6  0x0000000000412d94 in process_dinode (mp=0x7ffff8381580,
> dino=0x7fc9e2b38000, agno=0, ino=39869938, was_free=0,
> 
> dirty=0x7ffff8381390, cleared=0x7ffff838138c, used=0x7ffff8381394,
> ino_discovery=1, check_dups=0, extra_attr_check=1,
> 
> isa_dir=0x7ffff8381388, parent=0x7ffff8381398) at dinode.c:3017
> 
> #7  0x000000000040b607 in process_inode_chunk (mp=0x7ffff8381580,
> agno=0, num_inos=64, first_irec=0x751c810, ino_discovery=1,
> 
> check_dups=0, extra_attr_check=1, bogus=0x7ffff8381430) at
> dino_chunks.c:778
> 
> #8  0x000000000040bf46 in process_aginodes (mp=0x7ffff8381580,
> pf_args=0x75e6810, agno=0, ino_discovery=1, check_dups=0,
> 
> extra_attr_check=1) at dino_chunks.c:1025
> 
> #9  0x0000000000421db3 in process_ag_func (wq=0x1fe3790, agno=0,
> arg=0x75e6810) at phase3.c:162
> 
> #10 0x0000000000421f84 in process_ags (mp=0x7ffff8381580) at
> phase3.c:201
> 
> #11 0x00000000004220aa in phase3 (mp=0x7ffff8381580) at phase3.c:240
> 
> #12 0x000000000043bec4 in main (argc=5, argv=0x7ffff83818c8) at
> xfs_repair.c:697
> 
> 
> 
> 
> 
> I'll get the metadump on request.
> 
> 
> 
> 
> 
> Thanks for helping,
> 
> 
> 
> Jan
> 
> 
> 
> _______________________________________________ xfs mailing list 
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-09-04 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12 11:38 xfs_repair segfaulting in phase 3 Jan Yves Brueckner
2013-08-12 14:02 ` Eric Sandeen
2013-08-26 20:41 ` Eric Sandeen
2013-09-04 13:39 ` Eric Sandeen [this message]
2013-10-25 11:23   ` Aw: " Jan Yves Brueckner
2013-10-25 15:12     ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52273823.6050704@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=jyb@gmx.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.