| To: | Jan Yves Brueckner <jyb@xxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair segfaulting in phase 3 |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 26 Aug 2013 15:41:46 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <trinity-9e6d7620-812f-48a7-9a7e-3098368ff59a-1376307533158@3capp-gmx-bs36> |
| References: | <trinity-9e6d7620-812f-48a7-9a7e-3098368ff59a-1376307533158@3capp-gmx-bs36> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 |
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: ... Ok finally looking at the metadump you provided, thanks. But out of curiosity, what happened to this filesystem? Seems like a real mess. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Re: XFS: Assertion failed: first <= last && last < BBTOB(bp->b_length), file: fs/xfs/xfs_trans_buf.c, line: 568, Michael L. Semon |
|---|---|
| Next by Date: | [PATCH] xfs: don't leak root inode reference, Ben Myers |
| Previous by Thread: | Re: xfs_repair segfaulting in phase 3, Eric Sandeen |
| Next by Thread: | ***** SUSPECTED SPAM ***** [RFD 00/17] xfs: inode management development direction, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |