From: Florian Lindner <mailinglists@xgm.de>
To: linux-btrfs@vger.kernel.org
Subject: Can't mount: open_ctree failed!
Date: Sun, 02 Nov 2014 16:18:27 +0100 [thread overview]
Message-ID: <m35i04$u5p$1@ger.gmane.org> (raw)
Hello,
all after sudden I can't mount my btrfs home partition anymore. System is
Arch with kernel 3.17.2, but I use snapper which does snapshopts regularly
and I had 3.17.1 before, which afaik had some problems with snapshops.
Trying to mount without any options gives to the syslog:
Nov 02 16:04:16 horus kernel: BTRFS: mismatching generation and
generation_v2 found in root item. This root was probably mounted with an
older kernel. Resetting all new fields.
Nov 02 16:04:16 horus kernel: parent transid verify failed on 2121534193664
wanted 1073784832 found 45541
Nov 02 16:04:16 horus kernel: parent transid verify failed on 2121534193664
wanted 1073784832 found 45541
Nov 02 16:04:16 horus kernel: BTRFS: open_ctree failed
btrfsck quits after about half a minute with
# btrfsck /dev/sdb1
root item for root 3377, current bytenr 2122078191616, current gen
8589934592, current level 64, new bytenr 2122078191616, new gen 49443, new
level 1
root 3377 has a root item with a more recent gen (8589934592) compared to
the found root node (49443)
I also tried -s 0 or -s 1 or -b options to btrfsck, as well as
# btrfsck --init-extent-tree /dev/sdb1
root 3377 has a root item with a more recent gen (8589934592) compared to
the found root node (49443)
# btrfsck --init-csum-tree /dev/sdb1
Creating a new CRC tree
root 3377 has a root item with a more recent gen (8589934592) compared to
the found root node (49443)
Mounting with -o recovery gives exact the same error. My usual mount options
were defaults,compress=lzo,subvol=__current.
I also tried btrfs-zero-log but this does not change anything either.
Any ideas are deeply appreciated! Please help!
Florian
next reply other threads:[~2014-11-02 15:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 15:18 Florian Lindner [this message]
2014-11-02 22:31 ` Can't mount: open_ctree failed! Robert White
2014-11-03 8:24 ` Duncan
2014-11-03 16:35 ` Florian Lindner
2014-11-03 18:38 ` Chris Murphy
2014-11-03 19:48 ` Florian Lindner
2014-11-03 21:11 ` Chris Murphy
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='m35i04$u5p$1@ger.gmane.org' \
--to=mailinglists@xgm.de \
--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