Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Gour <gour@atmarama.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: pro/cons of raid1 with mdadm/lvm2
Date: Mon, 1 Dec 2014 10:42:36 +0500	[thread overview]
Message-ID: <20141201104236.1506b0a9@natsu> (raw)
In-Reply-To: <20141130121147.45884217@atmarama>

On Sun, 30 Nov 2014 12:11:47 +0100
Gour <gour@atmarama.net> wrote:

> However, I wonder if there are some 'cons' in having raid-1 partition
> under mdadm and not using native mirroring capabilities of btrfs fs?

Pros:

  * mdadm RAID has much better read balancing;
    Btrfs reads are satisfied from what's in effect a random drive (PID-based
    balancing of threads to drives), mdadm reads from the less-loaded drive.
    Also mdadm has a way to specify some RAID1 array members as to be never
    used for reads if at all possible ("write-mostly"), which helps in RAID1 of
    HDD and SSD.

  * mdadm RAID has much better write submission;
    In my experience [1] Btrfs RAID1 on heavy write operations first writes to
    one drive, then to another. The whole process takes up to 2x longer than
    with a single drive. On the other hand mdadm writes to both drives
    simultaneously.

[1] https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg34103.html

Con:

  * You only get the ability to recover from a checksum failure with Btrfs
    RAID1, not with mdadm RAID1 (see Russell's reply).

-- 
With respect,
Roman

  parent reply	other threads:[~2014-12-01  5:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 11:11 pro/cons of raid1 with mdadm/lvm2 Gour
2014-11-30 22:06 ` Russell Coker
2014-12-01  1:00   ` Chris Murphy
2014-12-01  8:18     ` Russell Coker
2014-12-01  9:30     ` Gour
2014-12-01  9:26   ` Gour
2014-12-01 18:19     ` Robert White
2014-12-01  5:42 ` Roman Mamedov [this message]
2014-12-01  9:33   ` Gour

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=20141201104236.1506b0a9@natsu \
    --to=rm@romanrm.net \
    --cc=gour@atmarama.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