From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Between single/dup and raid1/raid1
Date: Tue, 23 Oct 2012 20:49:32 +0200 [thread overview]
Message-ID: <20121023184932.GK2052@vicerveza.homeunix.net> (raw)
Hello,
today I wanted to remove one drive from raid1, and people at #btrfs advised me
to use '-dconvert=single' before 'btrfs device delete'.
I thought of adding '-mconvert=dup' too, but the kernel does not let me do that.
It looks like 'dup' is disallowed for an array of multiple devices. So, to go
back to a single-drive (single/dup) setup, should I go through having the
metadata with 'single' profile?
I can't use 'btrfs device delete' either, because that wouldn't respesct the
raid1 profile.
Maybe then the easiest I could do is to use the computer degraded, until I get
some new disk in some days? That'd be equivalent to metadata=single, as I
understand.
And having a totally new disk, having removed the broken one, I'd have to:
1) mount degraded
2) btrfs device delete the missing disk (will I be allowed? due to raid1 profile)
3) btrfs device add another disk
Should that work?
Regards,
Lluís.
reply other threads:[~2012-10-23 18:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121023184932.GK2052@vicerveza.homeunix.net \
--to=viric@viric.name \
--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).