From: Boris Chernov <aqs1024@hotmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Changing label few times killed filesystem?
Date: Tue, 25 Nov 2014 16:46:38 +0000 [thread overview]
Message-ID: <BLU436-SMTP14172AF9A2DA601C46C2DA0AB730@phx.gbl> (raw)
In-Reply-To: <pan$f37fb$4727340$23550eda$69bcec61@cox.net>
In attempt to get more information, I have commented out
BUG_ON(rec->is_root) in cmds-check.c to let btrfsck check my file system
without failing on this assertion. Below you can see the output. I would
appreciate any help or ideas...
# btrfsck /dev/sdb1 # Full log can be downloaded here:
http://pastebin.com/D68vr69J
Checking filesystem on /dev/sdb1
UUID: 787e3bc1-7583-4bd8-a52e-e57fd7fc9243
checking extents
...
ref mismatch on [20987904 16384] extent item 0, found 1
Backref 20987904 parent 3 root 3 not found in extent tree
backpointer mismatch on [20987904 16384]
owner ref check failed [20987904 16384]
...messages like these repeat many times, download full log to see them
all...
ref mismatch on [29540352 16384] extent item 0, found 1
Backref 29540352 parent 18446744073709551607 root 18446744073709551607
not found in extent tree
backpointer mismatch on [29540352 16384]
owner ref check failed [29540352 16384]
...
Errors found in extent allocation tree or chunk allocation
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
root 5 root dir 256 not found
found 409600 bytes used err is 1
total csum bytes: 0
total tree bytes: 49152
total fs tree bytes: 0
total extent tree bytes: 16384
btree space waste bytes: 48246
file data blocks allocated: 0
referenced 0
Btrfs v3.17
next prev parent reply other threads:[~2014-11-25 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 1:27 Changing label few times killed filesystem? Boris Chernov
2014-11-21 2:20 ` Chris Murphy
2014-11-21 11:47 ` Duncan
2014-11-21 4:35 ` Roman Mamedov
2014-11-21 8:49 ` Boris Chernov
2014-11-23 11:00 ` Boris Chernov
2014-11-24 2:46 ` Duncan
2014-11-25 11:04 ` Boris Chernov
2014-11-25 16:46 ` Boris Chernov [this message]
2014-11-27 18:27 ` Boris Chernov
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=BLU436-SMTP14172AF9A2DA601C46C2DA0AB730@phx.gbl \
--to=aqs1024@hotmail.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).