From: Chris Murphy <lists@colorremedies.com>
To: Rasmus Abrahamsen <btrfs@rasmusa.net>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Add big device, remove small device, read-only
Date: Sat, 2 Jan 2016 13:15:59 -0700 [thread overview]
Message-ID: <CAJCQCtSJp-p06VCrSaoeqAOFtnt=EfCMKfRF-DVkjpAiW9iv3A@mail.gmail.com> (raw)
In-Reply-To: <1451764729.3016753.481194250.0BE48A69@webmail.messagingengine.com>
On Sat, Jan 2, 2016 at 12:58 PM, Rasmus Abrahamsen <btrfs@rasmusa.net> wrote:
> What do you recommend I do? Everything is redundant across disks.
> Perhaps I can disconnect the one you mentioned and delete missing.
No, please stop trying new things like throwing spaghetti at a wall.
The file system is not healthy or it wouldn't behave the way it is. If
you have a current backup, and want to keep playing to see how bad
it'll get, then keep proceeding.
But if you have any important data on this volume that you don't have
a current backup for, then you need to make as few changes as
possible. Don't delete devices. Don't run btrfsck. Don't scrub. Don't
balance. Just try to get it mounted first, and then btrfs send, rsync,
or cp the data you need off the volume onto a new volume.
--
Chris Murphy
next prev parent reply other threads:[~2016-01-02 20:16 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
2016-01-02 19:56 ` Chris Murphy
2016-01-02 19:58 ` Rasmus Abrahamsen
2016-01-02 20:15 ` Chris Murphy [this message]
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='CAJCQCtSJp-p06VCrSaoeqAOFtnt=EfCMKfRF-DVkjpAiW9iv3A@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).