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 22:05:26 -0500 [thread overview]
Message-ID: <542234F6.4080000@hardwarefreak.com> (raw)
In-Reply-To: <5422285B.6010306@evermeet.cx>
On 09/23/2014 09:11 PM, Helmut Tessarek wrote:
> On 23.09.14 22:07 , Eric Sandeen wrote:
>> but! your raid doesn't have a 64k stripe, so that doesn't apply.
>
> Yep, that's true, but see below.
>
>> no geometry because md0 raid1 doesn't export any stripe geometry.
>
> [root@atvie01s ~]# cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 sdb1[0] sdd1[1]
> 3906784064 blocks super 1.2 [2/2] [UU]
> bitmap: 0/30 pages [0KB], 65536KB chunk
>
> So for some reason it shows a 64k chunk size even for RAID1.
>
> That was what got me confused.
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.
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 3:05 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 [this message]
2014-09-24 3:15 ` Helmut Tessarek
2014-09-24 4:09 ` Stan Hoeppner
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=542234F6.4080000@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