From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: do not check ram_bytes for non-compressed data extents
Date: Wed, 26 Jun 2024 08:14:41 +0930 [thread overview]
Message-ID: <a02831a2-ee8b-4e51-9782-3d9bbcd8b2f1@gmx.com> (raw)
In-Reply-To: <20240625151307.GV25756@twin.jikos.cz>
在 2024/6/26 00:43, David Sterba 写道:
> On Fri, Jun 21, 2024 at 07:52:06PM +0930, Qu Wenruo wrote:
>> This patch reverts the following 3 commits:
>> d0cc40d23aa0 ("btrfs-progs: tests: add test case for ram_bytes detection and repair")
>> 7313573c1942 ("btrfs-progs: check: original, detect and repair ram_bytes mismatch")
>> 97bf7a596900 ("btrfs-progs: check: lowmem, detect and repair mismatched ram_bytes")
>>
>> The problem with the ram_bytes check is, kernel can handle it without
>> any problem, and the original objective for this is to detect such
>> problem as I immaturelly believe the problem is fixed.
>>
>> But it turns out to be incorrect and this check is already causing
>> problems.
>>
>> Fix it by doing a full revert for now.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> Added to devel, thanks.
>
Just to mention, thankfully the root cause is found and the fix is
pretty small.
However I would still prefer to do the revert. Even with "minor errors"
mentioning, end users are still confused and asking for help.
So the lesson here is, we should really not to bother non-corruption
on-disk format violation in btrfs-check.
Just let kernel fix them silently, and with enough time they should
disappear anyway.
Thanks,
Qu
prev parent reply other threads:[~2024-06-25 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 10:22 [PATCH] btrfs-progs: do not check ram_bytes for non-compressed data extents Qu Wenruo
2024-06-25 15:13 ` David Sterba
2024-06-25 22:44 ` Qu Wenruo [this message]
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=a02831a2-ee8b-4e51-9782-3d9bbcd8b2f1@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--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