From: RK <rkasl@computer.org>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: Re: RAID-10 arrays built with btrfs & md report 2x difference in available size?
Date: Sun, 24 Jan 2010 07:01:35 -0500 [thread overview]
Message-ID: <4B5C369F.3020106@computer.org> (raw)
In-Reply-To: <c67eed301001232131n2a7f88acx857df19ea95371a4@mail.gmail.com>
.. I have the same puzzlement?
0bo0 wrote:
> I created a btrfs RAID-10 array across 4-drives,
>
> mkfs.btrfs -L TEST -m raid10 -d raid10 /dev/sda /dev/sdb /dev/sdc /dev/sdd
> btrfs-show
> Label: TEST uuid: 2ac85206-2d88-47d7-a1e7-a93d80b199f8
> Total devices 4 FS bytes used 28.00KB
> devid 1 size 931.51GB used 2.03GB path /dev/sda
> devid 2 size 931.51GB used 2.01GB path /dev/sdb
> devid 4 size 931.51GB used 2.01GB path /dev/sdd
> devid 3 size 931.51GB used 2.01GB path /dev/sdc
>
> @ mount,
>
> mount /dev/sda /mnt
> df -H | grep /dev/sda
> /dev/sda 4.1T 29k 4.1T 1% /mnt
>
> for RAID-10 across 4-drives, shouldn't the reported/available size be
> 1/2x4TB ~ 2TB?
>
> e.g., using mdadm to build a RAID-10 array across the same drives,
>
> mdadm -v --create /dev/md0 --level=raid10 --raid-devices=4 /dev/sd[abcd]1
> pvcreate /dev/md0
> pvs
> PV VG Fmt Attr PSize PFree
> /dev/md0 lvm2 -- 1.82T 1.82T
>
> is the difference in available array space real, an artifact, or a
> misunderstanding on my part?
>
> thanks.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-24 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 5:31 RAID-10 arrays built with btrfs & md report 2x difference in available size? 0bo0
2010-01-24 12:01 ` RK [this message]
2010-01-24 17:18 ` 0bo0
-- strict thread matches above, loose matches on Subject: below --
2010-01-29 21:57 Thomas Kupper
2010-01-29 22:13 ` 0bo0
2010-01-29 22:38 ` RK
2010-01-29 23:46 ` jim owens
2010-01-29 23:53 ` 0bo0
2010-01-30 13:24 ` Goffredo Baroncelli
2010-01-30 13:29 ` Goffredo Baroncelli
2010-01-30 15:36 ` jim owens
2010-02-08 3:52 ` 0bo0
2010-02-08 3:54 ` 0bo0
2010-02-08 14:33 ` jim owens
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=4B5C369F.3020106@computer.org \
--to=rkasl@computer.org \
--cc=linux-btrfs@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