From: Craig Johnson <crajohns@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfsck: couldn't open because of unsupported option features (8)
Date: Fri, 20 May 2011 08:08:16 -0500 [thread overview]
Message-ID: <BANLkTimkczntdTaPYOGznnPp6xfA+=wNSA@mail.gmail.com> (raw)
After upgrading from 2.6.39-rc7 to 2.6.39 this morning, I tried to
mount my 3 disk btrfs volume (no subvolumes, space caching enabled,
lzo compression) and received some parent transid errors (going back
to rc7 didn't help, though):
btrfs: disk space caching is enabled
parent transid verify failed on 6038227976192 wanted 337418 found 337853
parent transid verify failed on 6038227976192 wanted 337418 found 337853
parent transid verify failed on 6038227976192 wanted 337418 found 337853
parent transid verify failed on 6038227976192 wanted 337418 found 337853
parent transid verify failed on 6038227976192 wanted 337418 found 337853
Failed to read block groups: -5
btrfs: open_ctree failed
Tried to mount without space_cache give the same message.
Trying to run btrfsck (or btrfs-debug-tree), compiled from git gives me this:
couldn't open because of unsupported option features (8).
btrfsck: disk-io.c:683: open_ctree_fd: Assertion `!(1)' failed.
Aborted
I see an Ubuntu bug (748340 -
https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/748340)
with a similar output (they get an unsupported option features (2)
instead of (8)), but there isn't any resolution that I see. Is there
anything I can do to resolve this? I can't mount degraded or ro or
anything. Thanks!
next reply other threads:[~2011-05-20 13:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:08 Craig Johnson [this message]
2011-05-21 3:20 ` btrfsck: couldn't open because of unsupported option features (8) Craig Johnson
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='BANLkTimkczntdTaPYOGznnPp6xfA+=wNSA@mail.gmail.com' \
--to=crajohns@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).