From: Stan Hoeppner <stan@hardwarefreak.com>
To: Helmut Tessarek <tessarek@evermeet.cx>,
Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: How to format RAID1 correctly
Date: Tue, 23 Sep 2014 23:09:10 -0500 [thread overview]
Message-ID: <542243E6.1040302@hardwarefreak.com> (raw)
In-Reply-To: <5422376D.3000204@evermeet.cx>
On 09/23/2014 10:15 PM, Helmut Tessarek wrote:
> On 23.09.14 23:05 , stan hoeppner wrote:
>> It confuses many people who are new to md RAID1. The above is the
>> *bitmap* chunk size, not the array chunk size. There is no array chunk
>> size for RAID1 as there is no striping. You must have striping to have
>> chunks. With md RAID1 every 4KB page write is simply mirrored to each
>> physical disk.
>
> Thanks for the info. I'm used to big ass storage subsystems, but new to SW
> RAID. I seems I have some catching up to do.
If you create any striped arrays, especially parity arrays, with md make
sure to manually specify chunk size and match it to your workload. The
current default is 512KB. This is too large for a great many workloads,
specifically those that are metadata heavy or manipulate many small
files. 512KB wastes space and with parity arrays causes RMW, hammering
throughput and increasing latency.
Cheers,
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-24 4:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 0:46 How to format RAID1 correctly Helmut Tessarek
2014-09-24 2:05 ` Helmut Tessarek
2014-09-24 2:07 ` Eric Sandeen
2014-09-24 2:11 ` Helmut Tessarek
2014-09-24 2:21 ` Eric Sandeen
2014-09-24 2:30 ` Helmut Tessarek
2014-09-24 3:05 ` stan hoeppner
2014-09-24 3:15 ` Helmut Tessarek
2014-09-24 4:09 ` Stan Hoeppner [this message]
2014-09-24 15:53 ` Helmut Tessarek
2014-09-24 16:18 ` Eric Sandeen
2014-09-24 19:06 ` 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=542243E6.1040302@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=sandeen@sandeen.net \
--cc=tessarek@evermeet.cx \
--cc=xfs@oss.sgi.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