linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Kaiser <simon.kaiser@kit.edu>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: corrupt leaf; unaligned key offset for csum item
Date: Mon, 11 Jun 2018 00:32:18 +0200	[thread overview]
Message-ID: <87y3fm9sst.fsf@int-nb-181.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAJCQCtSrxUk0HBBVADKn202LpAhxhxxTek8Dycxv9gd8fJmsUQ@mail.gmail.com>

Chris Murphy <lists@colorremedies.com> writes:

>> 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?

Around the time of the error, dmesg shows only the btrfs error I
initially posted:

[   73.453640] BTRFS critical (device sda5): corrupt leaf: root=1 block=73263579136 slot=105, unaligned key offset for csum item, have 1271496708 should be aligned to 4096
[   73.791479] BTRFS critical (device sda5): corrupt leaf: root=1 block=73263579136 slot=105, unaligned key offset for csum item, have 1271496708 should be aligned to 4096

Yours,
Simon

  reply	other threads:[~2018-06-10 22:32 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 [this message]
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=87y3fm9sst.fsf@int-nb-181.i-did-not-set--mail-host-address--so-tickle-me \
    --to=simon.kaiser@kit.edu \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.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;
as well as URLs for NNTP newsgroup(s).