linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Monperrus <martin.monperrus@gnieh.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: How to repair a BTRFS block?
Date: Thu, 23 Apr 2015 20:05:16 +0200	[thread overview]
Message-ID: <5539345C.1040905@gnieh.org> (raw)
In-Reply-To: <55320BAE.1030007@gnieh.org>

Hi,

More on my issue, I have "uncorrectable errors"

# btrfs scrub status /
scrub status for e11013b3-b244-4d1a-a9c7-3956db1a699c
    scrub started at Thu Apr 23 19:07:45 2015 and finished after 372 seconds
    total bytes scrubbed: 167.13GiB with 13 errors
    error details: read=13
    corrected errors: 0, uncorrectable errors: 13, unverified errors: 0

Before going to my backups, how can know the files impacted by those
uncorrectable errors?

Best regards,

--Martin



On 04/18/2015 09:45 AM, Martin Monperrus wrote:
> Dear Btrfs developers,
>
> For some unknown reasons, my BTRFS filesystem is corrupted. dmesg prints
>
> |BTRFS critical (device sda2): corrupt leaf, slot offset bad:
> block=43231330304,root=1, slot=47|
>
> (more than 1000x in the dmesg trace).
>
> btrfs check --repair fails with:
>
> read block failed check_tree_block
> incorrect offset 12725 2298746482
> items overlap, can't fix
> cmds_check.c:2918: fix_item_offset: Assertion 'ret' failed
>
> How to list the files in block #43231330304 affected by the corruption?
> How to repair block #43231330304?
>
> Best regards,
>
> --Martin
>


  reply	other threads:[~2015-04-23 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-18  7:45 How to repair a BTRFS block? Martin Monperrus
2015-04-23 18:05 ` Martin Monperrus [this message]
2015-04-24  3:30   ` Duncan
2015-04-24 17:44   ` Martin Monperrus
2015-04-25  0:42     ` Duncan
2015-04-25  8:11       ` Duncan
2015-04-25 17:56     ` Martin Monperrus

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=5539345C.1040905@gnieh.org \
    --to=martin.monperrus@gnieh.org \
    --cc=linux-btrfs@vger.kernel.org \
    /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).