On 2020/2/26 上午8:51, Steven Fosdick wrote: > On Tue, 25 Feb 2020 at 23:59, Qu Wenruo <quwenruo.btrfs@xxxxxxx> 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:
signature.asc
Description: OpenPGP digital signature
