From: John Robinson <john.robinson@anonymous.org.uk>
To: Michal Soltys <soltys@ziu.info>
Cc: Pol Hallen <polhallen@fuckaround.org>,
Stan Hoeppner <stan@hardwarefreak.com>,
linux-raid@vger.kernel.org
Subject: Re: advice to low cost hardware raid (with mdadm)
Date: Fri, 17 Sep 2010 01:42:08 +0100 [thread overview]
Message-ID: <4C92B960.2050305@anonymous.org.uk> (raw)
In-Reply-To: <4C929D19.80001@ziu.info>
On 16/09/2010 23:41, Michal Soltys wrote:
> On 10-09-16 00:03, Pol Hallen wrote:
>>
>>> additionally, in the event
>>> of a disk failure, rebuilding a 6x1TB RAID5/6 array will take forever
>>> and a day.
>>
>> a nightmare...
>>
>> very thanks for your reasoning.. I don't have enought experience about
>> raid and friends!
>>
>> Pol
>
> One remark - write intent bitmaps will make it perfectly fine (orders of
> magnitude faster). I'm not sure how the feature looks from performance
> point of view these days though.
It should be configured with a sensible block size; the default block
size is usually too small and spoils performance. I chose a 16MB write
intent bitmap block size after experimenting a while ago (have a look
for posts on the subject from me), on the basis that larger gave
diminishing returns for write performance and smaller (nearer the
default) impacted badly on write performance, but others have gone as
big as 128MB (again see the archives), but the default, while it depends
on the array size and metadata version, often damages write performance
for only a small benefit in recovery time.
In short, the default write intent bitmap block size works but is liable
to be suboptimal so you should consider tuning it rather than take the
default.
Cheers,
John.
next prev parent reply other threads:[~2010-09-17 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 20:07 advice to low cost hardware raid (with mdadm) Pol Hallen
2010-09-15 20:41 ` Stan Hoeppner
2010-09-15 21:40 ` Keld Jørn Simonsen
2010-09-15 22:25 ` Stan Hoeppner
2010-09-16 12:05 ` Keld Jørn Simonsen
2010-09-15 22:03 ` Pol Hallen
2010-09-15 23:56 ` Stan Hoeppner
2010-09-16 22:41 ` Michal Soltys
2010-09-17 0:42 ` John Robinson [this message]
2010-09-17 4:38 ` Stan Hoeppner
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=4C92B960.2050305@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=linux-raid@vger.kernel.org \
--cc=polhallen@fuckaround.org \
--cc=soltys@ziu.info \
--cc=stan@hardwarefreak.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;
as well as URLs for NNTP newsgroup(s).