From: Gert Cuykens <gert.cuykens@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfsck disk explenation
Date: Tue, 16 Jul 2013 18:55:54 +0200 [thread overview]
Message-ID: <CAG7ytityYnSO_i5fCRDOYyzAcx5YzGqj2MgK4bMSmKXuwxqw1w@mail.gmail.com> (raw)
This is a nice overview
https://btrfs.wiki.kernel.org/index.php/Data_Structures but does not
show how things work. Would be helpful if there was a presentation
that shows what happens when for example you copy a file to understand
the use of each tree better?
I don't understand what went wrong in which tree?
parent transid verify failed (transid in root tree?)
leaf parent key incorrect (fs tree?)
bad block (csum tree does not match block?)
And finally can this be fixt?
root@v7:/srv# btrfsck disk
parent transid verify failed on 30113792 wanted 13 found 35
parent transid verify failed on 30113792 wanted 13 found 35
parent transid verify failed on 30113792 wanted 13 found 35
parent transid verify failed on 30113792 wanted 13 found 35
Ignoring transid failure
checking extents
parent transid verify failed on 61681664 wanted 9 found 33
parent transid verify failed on 61681664 wanted 9 found 33
parent transid verify failed on 61681664 wanted 9 found 33
parent transid verify failed on 61681664 wanted 9 found 33
Ignoring transid failure
leaf parent key incorrect 61681664
parent transid verify failed on 61681664 wanted 9 found 33
Ignoring transid failure
leaf parent key incorrect 61681664
parent transid verify failed on 61681664 wanted 9 found 33
Ignoring transid failure
leaf parent key incorrect 61681664
leaf parent key incorrect 29593600
bad block 29593600
parent transid verify failed on 29933568 wanted 13 found 34
parent transid verify failed on 29933568 wanted 13 found 34
parent transid verify failed on 29933568 wanted 13 found 34
parent transid verify failed on 29933568 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29933568
parent transid verify failed on 62836736 wanted 9 found 33
parent transid verify failed on 62836736 wanted 9 found 33
parent transid verify failed on 62836736 wanted 9 found 33
parent transid verify failed on 62836736 wanted 9 found 33
Ignoring transid failure
parent transid verify failed on 29962240 wanted 13 found 34
parent transid verify failed on 29962240 wanted 13 found 34
parent transid verify failed on 29962240 wanted 13 found 34
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
parent transid verify failed on 29962240 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
leaf parent key incorrect 29483008
bad block 29483008
leaf parent key incorrect 29548544
bad block 29548544
leaf parent key incorrect 29560832
bad block 29560832
bad block 29573120
leaf parent key incorrect 29581312
bad block 29581312
leaf parent key incorrect 29630464
bad block 29630464
leaf parent key incorrect 29691904
bad block 29691904
parent transid verify failed on 29933568 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29777920
bad block 29777920
leaf parent key incorrect 29904896
bad block 29904896
leaf parent key incorrect 29917184
bad block 29917184
leaf parent key incorrect 29933568
bad block 29933568
parent transid verify failed on 29933568 wanted 13 found 34
Ignoring transid failure
leaf parent key incorrect 29962240
bad block 29962240
leaf parent key incorrect 29970432
bad block 29970432
leaf parent key incorrect 29974528
bad block 29974528
leaf parent key incorrect 30068736
bad block 30068736
btrfsck: btrfsck.c:1935: check_owner_ref: Assertion `!(rec->is_root)' failed.
Aborted (core dumped)
root@v7:/srv#
reply other threads:[~2013-07-16 16:55 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=CAG7ytityYnSO_i5fCRDOYyzAcx5YzGqj2MgK4bMSmKXuwxqw1w@mail.gmail.com \
--to=gert.cuykens@gmail.com \
--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).