From: Chris Mason <chris.mason@oracle.com>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A bug with multiple devices?
Date: Tue, 30 Dec 2008 16:19:27 -0500 [thread overview]
Message-ID: <1230671967.4229.3.camel@think.oraclecorp.com> (raw)
In-Reply-To: <200812302214.32650.chris@csamuel.org>
On Tue, 2008-12-30 at 22:14 +1100, Chris Samuel wrote:
> On Tue, 30 Dec 2008 9:45:22 pm Chris Samuel wrote:
>
> > mkfs.btrfs -m raid1 /dev/sda10 /dev/sda11
>
> Even doing what appears to be the correct method of:
>
> mkfs.btrfs -d raid1 -m raid1 /dev/sda10 /dev/sda11
>
> doesn't give any love, mkfs.btrfs still tells me the filesystem will be 60GB
> (and the kernel agrees when it is mounted).
>
> But mkfs.btrfs does correctly set data_profile to include
> BTRFS_BLOCK_GROUP_RAID1 and does indeed call create_one_raid_group() with
> BTRFS_BLOCK_GROUP_DATA in create_raid_groups() in mkfs.c.
This is one of those things I've left for later.
Basically df tells you the total storage in the FS. This storage might
be raid0, raid1 or single spindle duplication, so the usable space may
be different from the total storage.
In the future we'll have the data sent to df give better estimates of
usable space.
Changing btrfs-show to show the chunks too is a good idea.
-chris
next prev parent reply other threads:[~2008-12-30 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 1:44 A bug with multiple devices? Shen Feng
2008-12-30 10:45 ` Chris Samuel
2008-12-30 11:14 ` Chris Samuel
2008-12-30 21:19 ` Chris Mason [this message]
2008-12-30 11:35 ` Yan Zheng
2008-12-30 12:03 ` Chris Samuel
2008-12-30 12:19 ` Chris Samuel
2008-12-31 1:11 ` Shen Feng
2008-12-31 1:17 ` Liu Hui
2008-12-31 1:43 ` Shen Feng
2009-01-01 0:52 ` Chris Samuel
2008-12-31 3:30 ` Shen Feng
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=1230671967.4229.3.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=chris@csamuel.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