All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl-Philipp Richter <krichter722@aol.de>
To: linux-btrfs@vger.kernel.org
Subject: `btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags & 1)' failed.` in `btrfsck`
Date: Fri, 18 Jul 2014 14:01:44 +0200	[thread overview]
Message-ID: <53C90CA8.2000104@aol.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 2627 bytes --]

Hi together,
I'm experiencing the following issues when I invoke `btrfsck` on a
sparse file image with a GPT and one (the only) btrfs partition attached
to a loop device

    $ sudo btrfsck --repair --init-csum-tree --init-extent-tree -b
/dev/loop0p1
    Incorrect local backref count on 128510738432 root 5 owner 3849475
offset 0 found 1 wanted 0 back 0xbab41270
    backpointer mismatch on [128510738432 4096]
    ref mismatch on [128510742528 12288] extent item 0, found 1
    btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags
& 1)' failed.

    $ sudo btrfsck --repair --init-csum-tree --init-extent-tree /dev/loop0p1
    Incorrect local backref count on 128510726144 root 5 owner 3849470
offset 0 found 1 wanted 0 back 0xbbcb9500
    backpointer mismatch on [128510726144 12288]
    ref mismatch on [128510738432 4096] extent item 0, found 1
    adding new data backref on 128510738432 root 5 owner 3849475 offset
0 found 1
    Backref 128510738432 root 5 owner 3849475 offset 0 num_refs 0 not
found in extent tree
    Incorrect local backref count on 128510738432 root 5 owner 3849475
offset 0 found 1 wanted 0 back 0xbbcb9630
    backpointer mismatch on [128510738432 4096]
    ref mismatch on [128510742528 12288] extent item 0, found 1
    btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags
& 1)' failed.

    $ sudo btrfsck --repair /dev/loop0p1
    Incorrect local backref count on 130861096960 root 5 owner 22733727
offset 0 found 1 wanted 0 back 0xc7c7d170
    backpointer mismatch on [130861096960 8192]
    ref mismatch on [130861105152 8192] extent item 0, found 1
    btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags
& 1)' failed.

    $ sudo btrfsck --repair /dev/loop0p1
    Backref 130861096960 root 5 owner 22733727 offset 0 num_refs 0 not
found in extent tree
    Incorrect local backref count on 130861096960 root 5 owner 22733727
offset 0 found 1 wanted 0 back 0xc7f31170
    backpointer mismatch on [130861096960 8192]
    ref mismatch on [130861105152 8192] extent item 0, found 1
    btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags
& 1)' failed.

I'm using `btrfs-progs` 24cf4d8c3ee924b474f68514e0167cc2e602a48d on
Linux 3.16-rc5 (anything else, i.e. older versions, give me immediate
error after start because errornous file system)

I'd like to know whether this (assertion) error is related to a bug or
missing feature in btrfs-progs and might be fixed at some point or
whether this might indicate a completely messed up btrfs.

Best regards,
Karl-P. Richter


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

             reply	other threads:[~2014-07-18 12:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 12:01 Karl-Philipp Richter [this message]
2014-07-18 12:13 ` `btrfsck: extent_io.c:612: free_extent_buffer: Assertion `!(eb->flags & 1)' failed.` in `btrfsck` Wang Shilong
2014-07-21 18:02   ` Karl-Philipp Richter

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=53C90CA8.2000104@aol.de \
    --to=krichter722@aol.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.