From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Steven Fosdick <stevenfosdick@gmail.com>, linux-btrfs@vger.kernel.org
Cc: Jonathan H <pythonnut@gmail.com>
Subject: Re: USB reset + raid6 = majority of files unreadable
Date: Wed, 26 Feb 2020 08:55:12 +0800 [thread overview]
Message-ID: <efc139cb-1d50-d227-e3dc-cbac359f46af@gmx.com> (raw)
In-Reply-To: <CAG_8rEf4BQpBPkYQywhMgg8Mw=-R8fs1KkE=n5qAz5XKevNM5Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3557 bytes --]
On 2020/2/26 上午8:51, Steven Fosdick wrote:
> On Tue, 25 Feb 2020 at 23:59, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>> On 2020/2/26 上午4:39, Jonathan H wrote:
>>> [ +2.697798] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 1
>>> [ +0.003381] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 2
>>> [ +0.002514] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 4
>>> [ +0.000543] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 1
>>> [ +0.001170] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 2
>>> [ +0.001151] BTRFS warning (device sdb): csum failed root -9 ino 257
>>> off 2083160064 csum 0xd0a0b14c expected csum 0x7f3ec5ab mirror 4
>>
>> This is a different error.
>> This means data reloc tree is corrupted.
>> This somewhat looks like an existing bug. especially when all rebuild
>> result the same csum.
>
> This looks remarkably similar to the errors I am getting that prevent
> removing a failed device from the array, except in my case it is only
> the found value is the same in the whole set of messages, the expected
> value varies. Do you know if/when this bug was/will be corrected?
> Can the reloc tree be repaired/rebuilt?
Data reloc tree is just a temporary tree for relocation.
Since it failed to pass csum, relocation will abort and cleanup the data
reloc tree.
>
> Here are the messages I am getting:
>
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494745088 csum 0x8941f998 expected csum
> 0x99726972 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494749184 csum 0x8941f998 expected csum
> 0x4c946d24 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494753280 csum 0x8941f998 expected csum
> 0x3cacfa54 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494757376 csum 0x8941f998 expected csum
> 0x453f4f60 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494761472 csum 0x8941f998 expected csum
> 0x5630f6fa mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494765568 csum 0x8941f998 expected csum
> 0xbf215c7a mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494769664 csum 0x8941f998 expected csum
> 0x242df5b3 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494773760 csum 0x8941f998 expected csum
> 0x84d8643c mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494777856 csum 0x8941f998 expected csum
> 0xcd4799e3 mirror 2
> Feb 22 20:08:01 meije kernel: BTRFS warning (device sda): csum failed
> root -9 ino 261 off 1494781952 csum 0x8941f998 expected csum
> 0x84e72065 mirror 2
Since the root is still -9, it's still data reloc tree and doesn't make
much sense.
BTW, full dmesg and btrfs check output are appreciated.
Thanks,
Qu
>
>
> Regards,
> Steve.
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-26 0:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 20:39 USB reset + raid6 = majority of files unreadable Jonathan H
2020-02-25 23:58 ` Qu Wenruo
2020-02-26 0:51 ` Steven Fosdick
2020-02-26 0:55 ` Qu Wenruo [this message]
2020-02-26 3:38 ` Jonathan H
2020-02-26 3:44 ` Jonathan H
2020-02-26 4:37 ` Qu Wenruo
2020-02-26 16:45 ` Jonathan H
2020-02-26 22:36 ` Steven Fosdick
2020-02-26 23:14 ` Steven Fosdick
2020-02-27 0:42 ` Chris Murphy
2020-02-27 0:39 ` Chris Murphy
2020-02-27 0:47 ` Chris Murphy
2020-02-27 12:20 ` Steven Fosdick
2020-02-27 12:35 ` Steven Fosdick
2020-02-29 6:31 ` Chris Murphy
2020-03-03 23:40 ` Steven Fosdick
2020-03-04 6:32 ` Chris Murphy
2020-03-04 12:45 ` Steven Fosdick
2020-03-04 20:10 ` Chris Murphy
2020-03-03 15:42 ` Jonathan H
2020-03-04 20:17 ` RooSoft Ltd @ bluehost
2020-03-09 21:10 ` Steven Fosdick
2020-03-11 4:41 ` Zygo Blaxell
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=efc139cb-1d50-d227-e3dc-cbac359f46af@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pythonnut@gmail.com \
--cc=stevenfosdick@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox