From: Leonidas Spyropoulos <artafinde@gmail.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unable to open ctree
Date: Sun, 2 Oct 2016 23:05:48 +0100 [thread overview]
Message-ID: <20161002220548.skncaa6iipyvwscs@tiamat> (raw)
In-Reply-To: <CAJCQCtRw+TMEDx9aPROdKSgbNDDw1PwkS2r8u-Lg_jyetv6wtQ@mail.gmail.com>
Hello,
After the command to rebuild the extent tree
# btrfs check --init-extent-tree --repair /dev/sda3
I was able to mount and run successfully a scrub (not sure if it would
detect something though).
Next was reboot and try to boot which was successful as well.
I'll keep an eye on the dmesh log next days but seems it's ok.
Thanks for suggestions all,
Regards,
--
Leonidas Spyropoulos
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
next prev parent reply other threads:[~2016-10-02 22:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 18:17 Unable to open ctree Leonidas Spyropoulos
2016-10-02 19:29 ` Chris Murphy
2016-10-02 20:12 ` Leonidas Spyropoulos
2016-10-02 20:22 ` Roman Mamedov
2016-10-02 20:27 ` Chris Murphy
2016-10-02 22:05 ` Leonidas Spyropoulos [this message]
2016-10-02 20:46 ` Leonidas Spyropoulos
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=20161002220548.skncaa6iipyvwscs@tiamat \
--to=artafinde@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