linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Simon Kaiser <simon.kaiser@kit.edu>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: corrupt leaf; unaligned key offset for csum item
Date: Sun, 10 Jun 2018 13:12:30 +0800	[thread overview]
Message-ID: <aa02c8c9-7ce7-eb8d-18e8-d810532083d8@gmx.com> (raw)
In-Reply-To: <CAJCQCtQzd=pKySzt1aJoABHw3kEYxUnJMqCAZhBnmxSNV43=EQ@mail.gmail.com>


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



On 2018年06月10日 11:53, Chris Murphy wrote:
> On Sat, Jun 9, 2018 at 7:56 PM, Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
>>
>> Indeed, the corrupted bytenr is 0x4bc98004.
>> Looks pretty like a bit flip in the 3rd lowest bit.
>>
>> It can be fixed by manually patching the corrupted leaf to get rid of
>> the bitflip.
>> I could provide a special branch of btrfs-progs to fix it easily.
>>
>> But before that, it's better to do a scrub to see if there is other
>> similar problems, so I could fix them all.
>>
> 
> Do you think Simon should try -o ro and -o ro,norecovery and see if he
> can update backups the easy way first?

If the bit flip is the only problem, I could fix it manually and nothing
is lost, the fs can be used as usual.

> And then use the offline scrub
> to check for additional problems?

I mean online scrub.

I didn't notice extra error, and I don't believe even for a faulty
memory, bit flip is that easy to happen, so on-line scrub should do the
work.

> 
> Simon, the offline scrub is done unmounted with 'btrfs check
> --check-data-csum <dev>' and it is a read-only check.
> 
> 


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

  reply	other threads:[~2018-06-10  5:12 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 [this message]
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

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=aa02c8c9-7ce7-eb8d-18e8-d810532083d8@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --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).