From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Sean Greenslade <sean@seangreenslade.com>,
Jim Murphy <srlinuxadmin@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Potential to loose data in case of disk failure
Date: Thu, 12 Nov 2015 07:47:16 -0500 [thread overview]
Message-ID: <56448A54.9020404@gmail.com> (raw)
In-Reply-To: <20151111202403.GA19245@wheatley.student.rit.edu>
[-- Attachment #1: Type: text/plain, Size: 2778 bytes --]
On 2015-11-11 15:24, Sean Greenslade wrote:
> On Wed, Nov 11, 2015 at 11:30:57AM -0600, Jim Murphy wrote:
>> Hi all,
>>
>> What am I missing or misunderstanding? I have a newly
>> purchased laptop I want/need to multi boot different OSs
>> on. As a result after partitioning I have ended up with two
>> partitions on each of the two internal drives(sda3, sda8,
>> sdb3 and sdb8). FWIW, sda3 and sdb3 are the same size
>> and sda8 and sdb8 are the same size. As an end result
>> I want one btrfs raid1 filesystem. For lack of better terms,
>> sda3 and sda8 "concatenated" together, sdb3 and sdb8
>> "concatenated" together and then mirroring "sda" to "sdb"
>> using only btrfs. So far have found no use-case to cover
>> this.
>>
>> If I create a raid1 btrfs volume using all 4 "devices" as I
>> understand it I would loose data if I were to loose a drive
>> because two mirror possibilities would be:
>>
>> sda3 mirrored to sda8
>> sdb3 mirrored to sdb8
>>
>> Is what I want to do possible without using MD-RAID and/or
>> LVM? If so would someone point me to the documentation
>> I missed. For whatever reason, I don't want to believe that
>> this can't be done. I want to believe that the code in btrfs
>> is smart enough to know that sda3 and sda8 are on the same
>> drive and would not try to mirror data between them except in
>> a test setup. I hope I just missed some documentation,
>> somewhere.
>>
>> Thanks in advance for your help. And last but not least,
>> thanks to all for your work on btrfs.
>>
>> Jim
>
> That's a pretty unusual setup, so I'm not surprised there's no quick and
> easy answer. The best solution in my opinion would be to shuffle your
> partitions around and combine sda3 and sda8 into a single partition.
> There's generally no reason to present btrfs with two different
> partitions on the same disk.
>
> If there's something that prevents you from doing that, you may be able
> to use RAID10 or RAID6 somehow. I'm not really sure, though, so I'll
> defer to others on the list for implementation details.
RAID10 has the same issue. Assume you have 1 block. This gets stored
as 2 copies, each with 2 stripes, with the stripes split symmetrically.
For this, call the first half of the first copy 1a, the second half
1b, and likewise for 2a and 2b with the second copy. 1a and 2a have
identical contents, and 1b and 2b have identical contents. It is fully
possible that you will end up with this block striped such that 1a and
2a are on one disk, and 1b and 2b on the other. Based on this, losing
one disk would mean losing half the block, which would mean based on how
BTRFS works that you would lose the whole block (because neither copy
would be complete).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-11-12 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 17:30 Potential to loose data in case of disk failure Jim Murphy
2015-11-11 20:24 ` Sean Greenslade
2015-11-12 12:47 ` Austin S Hemmelgarn [this message]
2015-11-12 17:23 ` Dmitry Katsubo
2015-11-12 17:55 ` Austin S Hemmelgarn
2015-11-13 14:51 ` Chris Murphy
2015-11-13 15:52 ` Austin S Hemmelgarn
2015-11-11 23:13 ` Chris Murphy
2015-11-12 5:07 ` Duncan
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=56448A54.9020404@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sean@seangreenslade.com \
--cc=srlinuxadmin@gmail.com \
/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