From: Dave Chinner <david@fromorbit.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/2] xfsprogs: improve metadump handling of corrupt inodes
Date: Thu, 17 Mar 2022 10:12:51 +1100 [thread overview]
Message-ID: <20220316231253.99577-1-david@fromorbit.com> (raw)
Hi folks,
These are metadata patches I wrote a while back when helping to
diagnose the amount of damage a RAID failure made to an XFS
filesystem. metadump doesn't handle corrupt inode forks particularly
well, and these patches fix the two cases that were tripped over
while trying to metadump the broken filesystem.
Cheers,
Dave.
next reply other threads:[~2022-03-16 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 23:12 Dave Chinner [this message]
2022-03-16 23:12 ` [PATCH 1/2] metadump: handle corruption errors without aborting Dave Chinner
2022-03-16 23:12 ` [PATCH 2/2] metadump: be careful zeroing corrupt inode forks 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=20220316231253.99577-1-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
/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