public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yan Zheng" <yanzheng@21cn.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 19:35:17 +0800	[thread overview]
Message-ID: <3d0408630812300335s4e7c6cf1x9a45ff187b80f83@mail.gmail.com> (raw)
In-Reply-To: <200812302145.25796.chris@csamuel.org>

2008/12/30 Chris Samuel <chris@csamuel.org>:
> On Tue, 30 Dec 2008 12:44:38 pm Shen Feng wrote:
>
>> I think the partition size is no correct since this is a raid-1 partition.
>> The size should be half.
>
> I've just run into this myself and so can confirm this issue on a btrfs
> filesystem with 2 devices, where it is created by doing:
>
> mkfs.btrfs -m raid1 /dev/sda10 /dev/sda11
>
> modprobe btrfs
>
> btrfsctl -a
>
> mount /dev/sda10 /home
>
> The df command shows it has twice the space I was expecting (61GB rather than
> 30GB).  The btrfs-show command shows that it has two devices but doesn't
> appear to contain any way to show the RAID level implemented.    I get the
> same outcome if I mount /dev/sda11 instead of sda10.
>
> Any ideas ?
>

This is a known bug. In btrfs, chunks are created dynamically and may have
different RAID configurations.  So it's difficult to compute the space
in advance.

Regards
Yan Zheng

  parent reply	other threads:[~2008-12-30 11:35 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
2008-12-30 11:35   ` Yan Zheng [this message]
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=3d0408630812300335s4e7c6cf1x9a45ff187b80f83@mail.gmail.com \
    --to=yanzheng@21cn.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