linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Mixing partitioned and non-partitioned discs in a RAID?
Date: Sat, 20 Aug 2016 06:52:10 +0000 (UTC)	[thread overview]
Message-ID: <pan$5e14a$65553781$21ea4bb9$dc874b@cox.net> (raw)
In-Reply-To: CAMPo9spd+GF18K7sDZDsfvqLQJYwt_YuYM_05KOnVFmw_Vsrhw@mail.gmail.com

Bearcat Şándor posted on Fri, 19 Aug 2016 22:00:17 -0600 as excerpted:

> I have a btrfs non-raid file system that i'd like to convert to raid10.
> This single device has my efi boot partion on it, so it's partitioned
> into sda1 and sda2. I have 3 other discs (sdc-sde) that i'd like to make
> partition-less systems and then add them to the first disc (sda) using
> the steps in the conversion section of the wiki
> (https://btrfs.wiki.kernel.org/index.php/
Using_Btrfs_with_Multiple_Devices#Conversion).
> 
> My concern in that i'll be mixing a partitioned and partition-less
> system.  Will that work or will i hose myself?

It should work fine as far as btrfs is concerned.

Since you mentioned raid10, however, it's worth noting a difference 
between btrfs raid10 and conventional raid10 that takes some people by 
surprise, tho I don't know whether it'll be a factor for you or not.  
Btrfs raid is per-chunk, not per-device, and different chunks can be 
assigned differently.  What that tends to mean in practice is that while 
with conventional raid10 you can lose a second device without loss of 
data as long as it's from the other raid1 underneath the raid0, with 
btrfs raid10, losing a second device is likely to lose data, because with 
the per-chunk assignment, it's relatively likely that the two bad devices 
will contain both copies of the data for at least some chunks.  So with 
btrfs raid10, don't expect to be able to lose more than one device 
without data-loss, no matter /which/ devices they are.

One way around that, that still retains the checksum error correction 
features of btrfs raid1/10, is to put btrfs raid1 on top of a pair of md/
dmraid0s.  That's normally considered a raid01 instead of a raid10 and is 
discouraged as it makes rebuild more difficult, but btrfs' checksummed 
data error detection and with raid1/10, correction from the remaining 
good copy, makes it worth doing anyway.   And that way you can for 
instance put one of the underlying raid0s in one data cabinet and the 
other in another, and lose the connection to everything in the one, 
without loss of data as raid0 on the other leg of the btrfs raid1 will 
still be operating.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2016-08-20  6:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20  4:00 Mixing partitioned and non-partitioned discs in a RAID? Bearcat Şándor
2016-08-20  6:02 ` Andrei Borzenkov
2016-08-20  6:52 ` Duncan [this message]
2016-08-20 15:21 ` Chris Murphy
2016-08-20 15:37   ` Chris Murphy
     [not found]   ` <BLU437-SMTP168169D258F02597287B2E92170@phx.gbl>
2016-08-21  0:36     ` Chris Murphy
2016-08-21  2:19       ` Duncan
2016-08-21  2:28         ` Bearcat Şándor
2016-09-12 22:21         ` Kai Krakow
2016-09-13  4:07           ` Duncan
2016-09-14 18:21             ` Kai Krakow
2016-09-13 15:55           ` 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='pan$5e14a$65553781$21ea4bb9$dc874b@cox.net' \
    --to=1i5t5.duncan@cox.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).