From: Neil Brown <neilb@suse.de>
To: "Trebor A. Rude" <treborrude@comcast.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Confused About Results of Constructing raid10 Array
Date: Mon, 13 Oct 2008 11:25:16 +1100 [thread overview]
Message-ID: <18674.38252.660086.361249@notabene.brown> (raw)
In-Reply-To: message from Trebor A. Rude on Saturday October 11
On Saturday October 11, treborrude@comcast.net wrote:
> And here's the detail:
>
> hyperion ~ # mdadm --detail /dev/md3
> /dev/md3:
> Version : 00.90
> Creation Time : Wed Oct 8 23:41:22 2008
> Raid Level : raid10
> Array Size : 878907840 (838.19 GiB 900.00 GB)
> Used Dev Size : 585938560 (558.79 GiB 600.00 GB)
...
>
> There are two things I don't understand here:
>
> Why does the "Layout" line say "near=1, far=2"? Does that indicate that there
> are three copies of every block? Even though I have three drives, I only
> wanted two copies of each block.
No. The total number of copies is (near * far). 2 in this case.
I can that might be confusing.
>
> Where's the rest of my space? I put 1800 GB (again, base 10) of space into the
> array, but the total of "Array Size" and "Used Dev Size" is only 1500 GB.
> Where's the other 300 GB? Was it lost to formatting?
Why are you adding these numbers???
There is 600GB total on each of 3 devices. That is a total of 1800GB.
You have two copies of each block of data, so there is room for 900GB
of data.
The "600GB" is the number shown in "Used Dev Size" - it is the space in
each device that is actually used.
The "900GB" is the "Array Size". It is the amount of available space
in the array.
It looks like it is doing exactly what you want.
NeilBrown
prev parent reply other threads:[~2008-10-13 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 14:27 Confused About Results of Constructing raid10 Array Trebor A. Rude
2008-10-13 0:25 ` Neil Brown [this message]
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=18674.38252.660086.361249@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=treborrude@comcast.net \
/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