linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Simon Kaiser <simon.kaiser@kit.edu>, linux-btrfs@vger.kernel.org
Subject: Re: corrupt leaf; unaligned key offset for csum item
Date: Tue, 12 Jun 2018 09:18:26 +0800	[thread overview]
Message-ID: <8fb5a8bc-8b5d-c82b-b0c4-8e209b6c17b1@gmx.com> (raw)
In-Reply-To: <87in6pe0ln.fsf@int-nb-181.i-did-not-set--mail-host-address--so-tickle-me>


[-- Attachment #1.1: Type: text/plain, Size: 3854 bytes --]



On 2018年06月12日 00:42, Simon Kaiser wrote:
>> On 2018年06月10日 09:56, Qu Wenruo wrote:
>>
>> Since there is no other csum error exposed by btrfs check/scrub, the fix
>> for this particular csum item key bit flip can be fetched here:
>> https://github.com/adam900710/btrfs-progs/tree/dirty_fix
>>
>> The usage will be (after the normal compile procedure)
>> $ ./btrfs-corrupt-block -X <device>
>>
>> It needs to be executed offline (the <device> must be unmounted).
>>
>> Thanks,
>> Qu
>>
> 
> Thank you very much, that fixed the issue :)
> 
> btrfs scrub now shows 5 checksum errors on a single file
> 
> [ 1869.456426] BTRFS warning (device sda5): checksum error at logical 1271386112 on dev /dev/sda5, physical 1271386112, root 257, inode 8016535, offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011
> 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal)                                                                                                          
> [ 1869.456429] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, flush 0, corrupt 1, gen 0
> [ 1869.457975] BTRFS warning (device sda5): checksum error at logical 1271390208 on dev /dev/sda5, physical 1271390208, root 257, inode 8016535, offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011
> 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal)                                                                                                          
> [ 1869.457978] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, flush 0, corrupt 2, gen 0
> [ 1869.459381] BTRFS warning (device sda5): checksum error at logical 1271394304 on dev /dev/sda5, physical 1271394304, root 257, inode 8016535, offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011
> 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal)                                                                                                          
> [ 1869.459383] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, flush 0, corrupt 3, gen 0
> [ 1869.460827] BTRFS warning (device sda5): checksum error at logical 1271398400 on dev /dev/sda5, physical 1271398400, root 257, inode 8016535, offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011
> 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal)                                                                                                          
> [ 1869.460829] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, flush 0, corrupt 4, gen 0
> [ 1869.462118] BTRFS warning (device sda5): checksum error at logical 1271402496 on dev /dev/sda5, physical 1271402496, root 257, inode 8016535, offset 655360, length 4096, links 1 (path: var/log/journal/31d9cc011
> 2694cdab3887013fb7bbcf9/system@d8ae7586248c492d8d51c44efd7316da-0000000000000001-00056e3429e252bb.journal)                                                                                                          
> [ 1869.462120] BTRFS error (device sda5): bdev /dev/sda5 errs: wr 1, rd 370, flush 0, corrupt 5, gen 0
> 
> I don't really need that file, can I simply delete it and forget about
> it or is there something else I should do?

Of course you can delete it, and if nothing else went wrong, it should
fix the problem.

And of course, remove that offending memory stick.

Thanks,
Qu

> 
> Yours,
> Simon
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2018-06-12  1:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 12:22 corrupt leaf; unaligned key offset for csum item Simon Kaiser
2018-06-09 22:53 ` Chris Murphy
2018-06-10  1:56 ` Qu Wenruo
2018-06-10  3:53   ` Chris Murphy
2018-06-10  5:12     ` Qu Wenruo
2018-06-10 13:38       ` Simon Kaiser
2018-06-10 21:30         ` Chris Murphy
2018-06-10 22:32           ` Simon Kaiser
2018-06-11  8:10   ` Qu Wenruo
2018-06-11 16:42     ` Simon Kaiser
2018-06-12  1:18       ` 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=8fb5a8bc-8b5d-c82b-b0c4-8e209b6c17b1@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=simon.kaiser@kit.edu \
    /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).