All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Dmitry Katsubo <dma_k@mail.ru>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Potential to loose data in case of disk failure
Date: Fri, 13 Nov 2015 09:51:06 -0500	[thread overview]
Message-ID: <CAJCQCtTFj2dPUw-sxda3B+_G_-9777S1UdNrGkEQMQsPqLxGBQ@mail.gmail.com> (raw)
In-Reply-To: <5644CB2F.8010302@mail.ru>

On Thu, Nov 12, 2015 at 12:23 PM, Dmitry Katsubo <dma_k@mail.ru> wrote:
> On 2015-11-12 13:47, Austin S Hemmelgarn wrote:
>>> 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).
>
> Does it equally apply to RAID1? Namely, if I create
>
> mkfs.btrfs -mraid1 -draid1 /dev/sda3 /dev/sda8
>
> then btrfs will "believe" that these are different drives and mistakenly
> think that RAID pre-condition is satisfied. Am I right?

Yes.


>If so then I
> think this is a trap, and mkfs.btrfs should at least warn (or require
> --force) if two partitions are on the same drive for raid1/raid5/raid10.

Does mdadm warn in the same situation? LVM?

There are some assumptions being made about the end user's
understanding of the system they're working on, and those assumptions
aren't unreasonable. But I'm not opposed to an informational message.



-- 
Chris Murphy

  parent reply	other threads:[~2015-11-13 14:51 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
2015-11-12 17:23     ` Dmitry Katsubo
2015-11-12 17:55       ` Austin S Hemmelgarn
2015-11-13 14:51       ` Chris Murphy [this message]
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=CAJCQCtTFj2dPUw-sxda3B+_G_-9777S1UdNrGkEQMQsPqLxGBQ@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=dma_k@mail.ru \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.