All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com, Ole Tange <tange@binf.ku.dk>
Subject: Re: xfs_repair segfaults
Date: Fri, 01 Mar 2013 16:32:19 -0600	[thread overview]
Message-ID: <51312C73.5060203@sandeen.net> (raw)
In-Reply-To: <20130301223116.GE23616@dastard>

On 3/1/13 4:31 PM, Dave Chinner wrote:
> On Fri, Mar 01, 2013 at 04:14:23PM -0600, Eric Sandeen wrote:
>> On 2/28/13 9:22 AM, Ole Tange wrote:
>>> I forced a RAID online. I have done that before and xfs_repair
>>> normally removes the last hour of data or so, but saves everything
>>> else.
>>>
>>> Today that did not work:
>>>
>>> /usr/local/src/xfsprogs-3.1.10/repair# ./xfs_repair -n /dev/md5p1
>>> Phase 1 - find and verify superblock...
>>> Phase 2 - using internal log
>>>         - scan filesystem freespace and inode maps...
>>> flfirst 232 in agf 91 too large (max = 128)
>>> Segmentation fault (core dumped)
>>
>> FWIW, the fs in question seems to need a log replay, so 
>> xfs_repair -n would find it in a worse state...
>> I had forgotten that xfs_repair -n won't complain about
>> a dirty log.  Seems like it should.
>>
>> But, the log is corrupt enough that it won't replay:
>>
>> XFS (loop0): Mounting Filesystem
>> XFS (loop0): Starting recovery (logdev: internal)
>> ffff88036e7cd800: 58 41 47 46 00 00 00 01 00 00 00 5b 0f ff ff 00  XAGF.......[....
>                                                      ^^
> It's detecting AGF 91 is corrupt....

Yep and that's what lights up when repair -L runs too.

Ole, you can xfs_mdrestore your metadump image and run test repairs on the result,
if you want a more realistic "dry run" of what repair would do.

-Eric

> Cheers,
> 
> Dave.
> 

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

  reply	other threads:[~2013-03-01 22:32 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 15:22 xfs_repair segfaults Ole Tange
2013-02-28 18:48 ` Eric Sandeen
2013-03-01  9:37   ` Ole Tange
2013-03-01 16:46     ` Eric Sandeen
2013-03-04  9:00       ` Ole Tange
2013-03-04 15:20         ` Eric Sandeen
2013-03-08 10:21           ` Ole Tange
2013-03-08 20:32             ` Eric Sandeen
2013-03-12 10:41               ` Ole Tange
2013-03-12 14:40                 ` Eric Sandeen
2013-03-12 11:37             ` Ole Tange
2013-03-12 14:47               ` Eric Sandeen
2013-03-01 11:17 ` Dave Chinner
2013-03-01 12:24   ` Ole Tange
2013-03-01 20:53     ` Dave Chinner
2013-03-04  9:03       ` Ole Tange
2013-03-04 23:23         ` Dave Chinner
2013-03-08 10:09           ` Ole Tange
2013-03-01 22:14 ` Eric Sandeen
2013-03-01 22:31   ` Dave Chinner
2013-03-01 22:32     ` Eric Sandeen [this message]
2013-03-01 23:55       ` Eric Sandeen
2013-03-04 12:47       ` Ole Tange
2013-03-04 15:17         ` Eric Sandeen
2013-03-04 23:11           ` Dave Chinner
  -- strict thread matches above, loose matches on Subject: below --
2013-05-06 12:06 Xfs_repair segfaults Filippo Stenico
2013-05-06 14:34 ` Eric Sandeen
2013-05-06 15:00   ` Filippo Stenico
     [not found]     ` <CADNx=Kv0bt3fNGW8Y24GziW9MOO-+b7fBGub4AYP70b5gAegxw@mail.gmail.com>
2013-05-07 13:20       ` Eric Sandeen
2013-05-07 13:36         ` Filippo Stenico
2013-05-07 18:20           ` Filippo Stenico
2013-05-08 17:30             ` Filippo Stenico
2013-05-08 17:42               ` Filippo Stenico
2013-05-08 23:39               ` Dave Chinner
2013-05-09 15:11                 ` Filippo Stenico
2013-05-09 17:22                   ` Filippo Stenico
2013-05-09 22:39                     ` Dave Chinner
     [not found]                       ` <CADNx=KuQjMNHUk6t0+hBZ5DN6s=RXqrPEjeoSxpBta47CJoDgQ@mail.gmail.com>
2013-05-10 11:00                         ` Filippo Stenico
2013-05-09 22:37                   ` Dave Chinner

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=51312C73.5060203@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=david@fromorbit.com \
    --cc=tange@binf.ku.dk \
    --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.