From: Josef Bacik <josef@toxicpanda.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/3] btrfs-progs: check/lowmem: add inode transid detect and repair support
Date: Wed, 26 Aug 2020 10:34:27 -0400 [thread overview]
Message-ID: <2df29c40-4b52-4230-7785-dd8c4e5ca6be@toxicpanda.com> (raw)
In-Reply-To: <20200826005233.90063-2-wqu@suse.com>
On 8/25/20 8:52 PM, Qu Wenruo wrote:
> There are quite some reports on kernel rejecting invalid inode
> generation, but it turns out to be that, kernel is just rejecting inode
> transid. It's a bug in kernel error message.
>
> To solve the problem and make the fs mountable again, add the detect and
> repair support for lowmem mode.
>
> The implementation is pretty much the same, just re-use the existing
> inode generation detect and repair code.
>
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2020-08-26 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 0:52 [PATCH 0/3] btrfs-progs: check: add inode invalid transid detect and repair support Qu Wenruo
2020-08-26 0:52 ` [PATCH 1/3] btrfs-progs: check/lowmem: add inode " Qu Wenruo
2020-08-26 14:34 ` Josef Bacik [this message]
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=2df29c40-4b52-4230-7785-dd8c4e5ca6be@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).