From: Tomasz Mloduchowski <q@qdot.me>
To: linux-btrfs@vger.kernel.org
Subject: btrfsck - process_inode_item: Assertion `!(rec->ino != key->objectid || rec->refs > 1)' failed
Date: Wed, 09 Apr 2014 21:40:20 +0200 [thread overview]
Message-ID: <5345A224.2050801@qdot.me> (raw)
Hi,
I'm experiencing the following error when performing btrfsck --repair on
the damaged filesystem (some files indicate 'stale NFS handle' errors
when accessing).
checking extents
parent transid verify failed on 199000064 wanted 1868 found 1586
parent transid verify failed on 199000064 wanted 1868 found 1586
parent transid verify failed on 199000064 wanted 1868 found 1586
parent transid verify failed on 199000064 wanted 1868 found 1586
Ignoring transid failure
leaf parent key incorrect 199000064
bad block 199000064
Chunk[256, 228, 1103101952]: length(1073741824), offset(1103101952),
type(1) is not found in block group
-- snip --
Chunk[256, 228, 111121793024]: length(1023410176), offset(111121793024),
type(1) is not found in block group
Errors found in extent allocation tree or chunk allocation
checking free space cache
checking fs roots
parent transid verify failed on 199000064 wanted 1868 found 1586
Ignoring transid failure
-- snip --
parent transid verify failed on 199000064 wanted 1868 found 1586
Ignoring transid failure
btrfsck: cmds-check.c:512: process_inode_item: Assertion `!(rec->ino !=
key->objectid || rec->refs > 1)' failed.
The image (btrfs-image -s -c 9 -t 4) of this filesystem is available here:
http://static.qdot.me/home-btrfs-fail-2.img
btrfs-progs:
commit 761650b628d3b8964cc55da68ad5c8187f55c543
Thanks a lot for pointers or assistance (or patches to try out).
Cheers,
Tomasz
reply other threads:[~2014-04-09 17:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5345A224.2050801@qdot.me \
--to=q@qdot.me \
--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).