From: Chris Murphy <lists@colorremedies.com>
To: Rasmus Abrahamsen <btrfs@rasmusa.net>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Add big device, remove small device, read-only
Date: Sat, 2 Jan 2016 12:57:54 -0700 [thread overview]
Message-ID: <CAJCQCtSyYDgtUsPcTig11bGWq=f8rksTYXMtmW_FwdsRGCA=gQ@mail.gmail.com> (raw)
In-Reply-To: <1451764030.3014437.481190514.24FF8F10@webmail.messagingengine.com>
On Sat, Jan 2, 2016 at 12:47 PM, Rasmus Abrahamsen <btrfs@rasmusa.net> wrote:
> The scrub was frozen. I tried to cancel it but it had become read-only.
> I rebooted and am now looking into what btrfsck can do for me
Stay away from btrfs check --repair until it's a last restort. As in,
you have to have all data scraped off the volume before you decide to
use it. It's gotten a lot better at not making things worse, but I
still don't trust it.
--
Chris Murphy
next prev parent reply other threads:[~2016-01-02 19:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 11:47 Add big device, remove small device, read-only Rasmus Abrahamsen
2016-01-01 16:39 ` Duncan
2016-01-01 20:07 ` Chris Murphy
2016-01-01 20:20 ` Rasmus Abrahamsen
2016-01-02 10:08 ` Rasmus Abrahamsen
2016-01-02 11:03 ` Rasmus Abrahamsen
[not found] ` <13CBB600-0779-40B7-BD20-ED571A3336D7@rasmusa.net>
2016-01-02 16:45 ` Rasmus Abrahamsen
2016-01-02 19:47 ` Rasmus Abrahamsen
2016-01-02 19:57 ` Chris Murphy [this message]
2016-01-02 19:56 ` Chris Murphy
2016-01-02 19:58 ` Rasmus Abrahamsen
2016-01-02 20:15 ` Chris Murphy
2016-01-02 20:32 ` Chris Murphy
2016-01-02 20:39 ` Rasmus Abrahamsen
2016-01-02 21:28 ` Chris Murphy
2016-01-02 21:30 ` Rasmus Abrahamsen
2016-01-02 21:37 ` Chris Murphy
2016-01-02 21:42 ` Rasmus Abrahamsen
2016-01-02 22:46 ` Chris Murphy
2016-01-03 10:29 ` Rasmus Abrahamsen
2016-01-06 6:45 ` Duncan
2016-01-06 11:04 ` Rasmus Abrahamsen
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='CAJCQCtSyYDgtUsPcTig11bGWq=f8rksTYXMtmW_FwdsRGCA=gQ@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=btrfs@rasmusa.net \
--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).