From: Dave Chinner <david@fromorbit.com>
To: Sean Caron <scaron@umich.edu>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] metadump: handle corruption errors without aborting
Date: Thu, 3 Feb 2022 09:05:59 +1100 [thread overview]
Message-ID: <20220202220559.GB59729@dread.disaster.area> (raw)
In-Reply-To: <CAA43vkUFW3Y_0L7dFc+iAySdf4j3cX4M9Xoz+3eU4raoavmnew@mail.gmail.com>
On Wed, Feb 02, 2022 at 03:18:34PM -0500, Sean Caron wrote:
> Hi Dave,
>
> It counted up to inode 13555712 and then crashed with the error:
>
> malloc_consolidate(): invalid chunk size
That sounds like heap corruption or something similar - that's a
much more difficult problem to track down.
Can you either run gdb on the core file it left and grab a stack
trace of where it crashed, or run metadump again from gdb so that it
can capture the crash and get a stack trace that way?
> Immediately before that, it printed:
>
> xfs_metadump: invalid block number 4358190/50414336 (1169892770398976)
> in bmap extent 0 in symlink ino 98799839421
I don't think that would cause any problems - it just aborts
processing the extent records in that block and moves on to the next
valid one that is found.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-02-02 22:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 23:07 XFS disaster recovery Sean Caron
2022-02-01 23:33 ` Dave Chinner
2022-02-02 1:20 ` Sean Caron
2022-02-02 2:44 ` Dave Chinner
2022-02-02 7:42 ` [PATCH] metadump: handle corruption errors without aborting Dave Chinner
2022-02-02 18:49 ` Sean Caron
2022-02-02 19:43 ` Sean Caron
2022-02-02 20:18 ` Sean Caron
2022-02-02 22:05 ` Dave Chinner [this message]
2022-02-02 23:45 ` Sean Caron
2022-02-06 22:34 ` Dave Chinner
2022-02-07 21:42 ` Sean Caron
2022-02-07 22:34 ` Dave Chinner
2022-02-07 22:03 ` XFS disaster recovery Sean Caron
2022-02-07 22:33 ` Dave Chinner
2022-02-07 22:56 ` Sean Caron
2022-02-08 1:51 ` Dave Chinner
2022-02-08 15:46 ` Sean Caron
2022-02-08 20:56 ` Dave Chinner
2022-02-08 21:24 ` Sean Caron
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=20220202220559.GB59729@dread.disaster.area \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=scaron@umich.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox