linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carlos Mennens <carloswill@gmail.com>
To: Mdadm <linux-raid@vger.kernel.org>
Subject: Re: RAID1 On 3 Drives
Date: Mon, 15 Mar 2010 09:47:25 -0500	[thread overview]
Message-ID: <d80f793f1003150747h203aa5c4kc80375f4250f4532@mail.gmail.com> (raw)
In-Reply-To: <70ed7c3e1003150548v65dce098ud62ddfbcc0747d49@mail.gmail.com>

On Mon, Mar 15, 2010 at 7:48 AM, Majed B. <majedb@gmail.com> wrote:
> Carlos,
>
> Choosing your RAID setup depends on the purpose of your machine. Is it
> a web server, file server, archive, mail, video storage, ...etc.

Basically this is my everyday workstation that I keep everything on.
It's not hosting Apache or MySQL or anything like that. Just my
everyday workstation.

> /boot is only used during boot up. Having a spare on stand by or not
> does not affect performance, except in the case a disk dies; in that
> case, the hot spare is engaged and becomes an active disk at which the
> array starts to resync the data to this new disk. During resyncing,
> performance will be degraded.

Oh, I was wondering why Bill noted previously that a spare would hurt
performance but based on your info above, this is only if a drive
fails and then the spare starts to synchronize. I hope that is what
Bill meant.

> As for your RAID5 question: I think if your usage of the server is
> write-mostly, you may find it to have better performance with 3 disks
> rather 4. If it's read-mostly, then 4 disks should perform better.
>
> If you have physical access to the machine, try both cases. Setting
> them up won't take more than 5-10 minutes. Benchmarking wouldn't take
> more than 15 minutes in each setup.
>
> Remember, there are parameters to fine-tune: NCQ, read-ahead, noatime,
> nodiratime, chunksize, ...etc.

I do have access to the machine as it's my new Desktop PC I am
building today at some point. I just wanted to get some expert advise
on how I should proceed. For now I am going to use all 4 disks with no
spares.

I just don't know enough about fine tuning and how it could benefit or
hinder disk performance for my setup so I guess I will omit them until
I can understand what to use for what function. If you guys have any
suggestions for what parameters to use for /boot, /, or swap...please
feel free to chime in.

Thanks all!

  reply	other threads:[~2010-03-15 14:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-13 22:30 RAID1 On 3 Drives Joachim Otahal
2010-03-13 23:18 ` Carlos Mennens
2010-03-13 23:50   ` Bill Davidsen
2010-03-15 12:30     ` Carlos Mennens
2010-03-15 12:48       ` Majed B.
2010-03-15 14:47         ` Carlos Mennens [this message]
2010-03-15 16:05           ` Majed B.
2010-03-16  1:46             ` Keld Simonsen
2010-03-20 16:08       ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2010-03-13 21:06 Carlos Mennens
2010-03-13 21:21 ` Majed B.
2010-03-13 21:24   ` Carlos Mennens
2010-03-14 21:09     ` Luca Berra
2010-03-13 21:45   ` Neil Brown
2010-03-13 21:26 ` Neil Brown
2010-03-13 21:31   ` Majed B.
2010-03-13 21:50     ` Neil Brown
2010-03-14  3:30       ` Majed B.
2010-03-14  1:22 ` thib

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=d80f793f1003150747h203aa5c4kc80375f4250f4532@mail.gmail.com \
    --to=carloswill@gmail.com \
    --cc=linux-raid@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).