From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Tyler Richmond <t.d.richmond@gmail.com>
Subject: [PATCH 0/3] btrfs-progs: check: add inode invalid transid detect and repair support
Date: Wed, 26 Aug 2020 08:52:30 +0800 [thread overview]
Message-ID: <20200826005233.90063-1-wqu@suse.com> (raw)
Really nothing interesting here for btrfs-progs, just reusing existing
inode generation detect and repair code.
The interesting part is, how a wrongly copied error message delayed us
so long to locate a bug.
Reported-by: Tyler Richmond <t.d.richmond@gmail.com>
Qu Wenruo (3):
btrfs-progs: check/lowmem: add inode transid detect and repair support
btrfs-progs: check/original: add inode transid detect and repair
support
btrfs-progs: tests/fsck: add test image for inode transid repair
check/main.c | 8 +++++---
check/mode-lowmem.c | 11 +++++++----
.../bad_inode_transid.img.xz | Bin 0 -> 1888 bytes
3 files changed, 12 insertions(+), 7 deletions(-)
create mode 100644 tests/fsck-tests/043-bad-inode-generation/bad_inode_transid.img.xz
--
2.28.0
next reply other threads:[~2020-08-26 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 0:52 Qu Wenruo [this message]
2020-08-26 0:52 ` [PATCH 1/3] btrfs-progs: check/lowmem: add inode transid detect and repair support Qu Wenruo
2020-08-26 14:34 ` Josef Bacik
2020-08-26 0:52 ` [PATCH 2/3] btrfs-progs: check/original: " Qu Wenruo
2020-08-26 14:35 ` Josef Bacik
2020-08-26 0:52 ` [PATCH 3/3] btrfs-progs: tests/fsck: add test image for inode transid repair Qu Wenruo
2020-08-26 14:35 ` Josef Bacik
2020-08-31 15:09 ` [PATCH 0/3] btrfs-progs: check: add inode invalid transid detect and repair support David Sterba
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=20200826005233.90063-1-wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=t.d.richmond@gmail.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.