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 11:04:16 +0000 [thread overview]
Message-ID: <BLU436-SMTP1997275109CCFECC0054843AB730@phx.gbl> (raw)
In-Reply-To: <pan$f37fb$4727340$23550eda$69bcec61@cox.net>
On 2014-11-24 02:46, Duncan wrote
> if you were using gmane's web service, that explains things as
weaverd, the process
> that does the threading on the web side, was down for some days
Yes, I have used gmane blog. Good to know it is not down anymore.
Back on topic. Even after updating to the latest version, btrfsck
or any of its options including --repair still do not work. Does anyone
know what "Assertion `rec->is_root` failed" means? Is it worth trying to
compile my own version of btrfsck without this assertion?
With or without --repair option, it looks like this assertion stops
btrfsck very early, preventing btrfsck from checking the filesystem or
attempting to repair it.
# btrfsck /dev/sdb1
Checking filesystem on /dev/sdb1
UUID: 787e3bc1-7583-4bd8-a52e-e57fd7fc9243
checking extents
cmds-check.c:2645: check_owner_ref: Assertion `rec->is_root` failed.
btrfs check[0x41a081]
btrfs check[0x41a0a5]
btrfs check[0x409783]
btrfs check[0x40a45e]
btrfs check[0x41bfa9]
btrfs check[0x40b46a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fb275f24b45]
btrfs check[0x40b497]
# btrfsck --repair /dev/sdb1
enabling repair mode
Fixed 0 roots.
Checking filesystem on /dev/sdb1
UUID: 787e3bc1-7583-4bd8-a52e-e57fd7fc9243
checking extents
cmds-check.c:2645: check_owner_ref: Assertion `rec->is_root` failed.
btrfs check[0x41a081]
btrfs check[0x41a0a5]
btrfs check[0x409783]
btrfs check[0x40a45e]
btrfs check[0x41bfa9]
btrfs check[0x40b46a]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fbc5b8dab45]
btrfs check[0x40b497]
next prev parent reply other threads:[~2014-11-25 11:04 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 [this message]
2014-11-25 16:46 ` Boris Chernov
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-SMTP1997275109CCFECC0054843AB730@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).