From: Johannes Rohr <jorohr@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Subject: Re: backref mismatch / backpointer mismatch
Date: Thu, 10 Sep 2020 07:36:38 +0200 [thread overview]
Message-ID: <895dd934-8159-e14b-de7a-10fba881d96f@gmail.com> (raw)
In-Reply-To: <f4317021-89e4-904b-6032-10bdfe455450@gmx.com>
[-- Attachment #1.1: Type: text/plain, Size: 1087 bytes --]
Am 10.09.20 um 04:16 schrieb Qu Wenruo:
>
> On 2020/9/9 下午10:51, Johannes Rohr wrote:
> What about `btrfs check --mode=lowmem` result?
Too late already. After getting the green light in #btrfs, I ran the
--repair and it fixed the issue.
>
> If your btrfs-progs is not uptodate, it may be a false alert.
The reason why I did the offline check in the first place was that there
were issues, namely, that btrfs balance start -musage=70 / resulted in a
segfault and also my attempts to remove a faulty sdd from the RAID
reproducibly led to a kernel oops and a hung filesystem. I had asked
about this two times on the list [1] also reported the issue to the
kernel bugzilla [2]. Also, upgraded btrfs-progs to 5.7 before running
the test.
Fortunately --repair has fixed these issues.
Cheers,
Johannes
[1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg88916.html
[2] , https://bugzilla.kernel.org/show_bug.cgi?id=209143
>
> Thanks,
> Qu
>> Thanks so much in advance for your advice,
>>
>> Johannes
>>
>>
>>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-09-10 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 14:51 backref mismatch / backpointer mismatch Johannes Rohr
2020-09-10 2:16 ` Qu Wenruo
2020-09-10 5:36 ` Johannes Rohr [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=895dd934-8159-e14b-de7a-10fba881d96f@gmail.com \
--to=jorohr@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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