All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: "Nuno Magalhães" <nunomagalhaes@eu.ipp.pt>, linux-raid@vger.kernel.org
Subject: Re: RAID newbie, 1 vs 5, chunk sizes
Date: Mon, 16 Jun 2014 16:13:08 -0400	[thread overview]
Message-ID: <539F4FD4.9070504@turmel.org> (raw)
In-Reply-To: <CADqA9ubBicDLwrdgOYNT04P0SO8pi+FK-ipjONY+59ThV0zGKw@mail.gmail.com>

On 06/16/2014 12:14 PM, Nuno Magalhães wrote:
> Thanks for the tips.

> Back to a previous question (assuming i have the drives sorted out first):
> 
> If i create a RAID10 with 3 1TB drives, with --layout=f2, would this
> give me 2TB of space +1TB redundancy? Is this a 1E?
> Using: mdadm --create /dev/md0 --verbose --chunk=128 --level=10
> --layout=f2 --raid-devices=3 /dev/sd[abd]1

No, you'll have 1.5T of available space mirrored by halves.

> If so, what would be the difference to a RAID5:
> mdadm --create /dev/md0 --verbose --chunk=512 --level=5
> --raid-devices=3 /dev/sd[abd]1
> 
> Besides one having redundancy and the other having parity; and that
> RAID5 must compute parity (is that really so horrendously slow
> nowadays?).

You can't fit the redundancy for 2T of data into 1T without some form of
parity raid.

> Other than tiobench, any other benchmarking tools you guys recommend?
> (I've decided to just go slow and test every layer out before moving
> to the next, i.e. 1st RAID, LVM, FSs, Xen, apps.)

I'll leave that one for others. . .  Just don't expect dd to be very useful.

Phil

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-06-16 20:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-14 21:01 RAID newbie, 1 vs 5, chunk sizes Nuno Magalhães
2014-06-14 21:56 ` Stan Hoeppner
2014-06-15 11:50   ` Nuno Magalhães
     [not found]     ` <pmrj5x4rq3qbl6unnu7guho9.1402849407134@email.android.com>
2014-06-15 17:40       ` Nuno Magalhães
2014-06-16  2:23 ` Phil Turmel
2014-06-16 12:36   ` Nuno Magalhães
2014-06-16 13:19     ` Mark Knecht
2014-06-16 14:28     ` Phil Turmel
2014-06-16 16:14       ` Nuno Magalhães
2014-06-16 20:13         ` Phil Turmel [this message]
2014-06-16 21:02           ` Mark Knecht
2014-06-17  0:41         ` Nuno Magalhães
2014-06-17  0:47           ` Brad Campbell
2014-06-17  9:09             ` Nuno Magalhães
2014-06-17 19:50               ` Stan Hoeppner
2014-06-18  2:55               ` Brad Campbell
2014-06-18  7:33     ` Wilson, Jonathan
2014-06-18 10:19     ` Dag Nygren
2014-06-18 11:58       ` Mathias Burén
2014-06-18 12:16         ` Brad Campbell
2014-06-18 17:34         ` Roman Mamedov
2014-06-19  6:45           ` Wilson, Jonathan
2014-06-29 13:22             ` Nuno Magalhães

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=539F4FD4.9070504@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=nunomagalhaes@eu.ipp.pt \
    /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.