From: Chris Murphy <lists@colorremedies.com>
To: Simon Kaiser <simon.kaiser@kit.edu>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: corrupt leaf; unaligned key offset for csum item
Date: Sun, 10 Jun 2018 15:30:54 -0600 [thread overview]
Message-ID: <CAJCQCtSrxUk0HBBVADKn202LpAhxhxxTek8Dycxv9gd8fJmsUQ@mail.gmail.com> (raw)
In-Reply-To: <87wov63gnq.fsf@int-nb-181.i-did-not-set--mail-host-address--so-tickle-me>
On Sun, Jun 10, 2018 at 7:38 AM, Simon Kaiser <simon.kaiser@kit.edu> wrote:
> Qu Wenruo <quwenruo.btrfs@gmx.com> writes:
>
>> 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.
>>>>
>
> Online scrub `btrfs scrub start -B -r /mnt/` (`mount -o ro,norecovery`)
>
> ERROR: scrubbing /mnt/ failed for device id 1: ret=-1, errno=5 (Input/output error)
> scrub canceled for 95b4974b-a798-44b3-99aa-a4eef990aeeb
> scrub started at Sun Jun 10 13:25:37 2018 and was aborted after 00:00:03
> total bytes scrubbed: 1.09GiB with 0 errors
Is there any kernel message at the time of this i/o error? Either
Btrfs or device error?
--
Chris Murphy
next prev parent reply other threads:[~2018-06-10 21:30 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 [this message]
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=CAJCQCtSrxUk0HBBVADKn202LpAhxhxxTek8Dycxv9gd8fJmsUQ@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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).