From: jim owens <jowens@hp.com>
To: 0bo0 <0.bugs.only.0@gmail.com>
Cc: RK <rkasl@computer.org>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: RAID-10 arrays built with btrfs & md report 2x difference in available size?
Date: Mon, 08 Feb 2010 09:33:35 -0500 [thread overview]
Message-ID: <4B7020BF.4010302@hp.com> (raw)
In-Reply-To: <c67eed301002071954n2c8500adrd634b914cfe34484@mail.gmail.com>
0bo0 wrote:
> On Sat, Jan 30, 2010 at 7:36 AM, jim owens <jowens@hp.com> wrote:
>> So Josef Bacik has sent patches to btrfs and btrfs-progs that
>> allow you to see raid-mode data and metadata adjusted values
>> with btrfs-ctrl -i instead of using "df".
>>
>> These patches have not been merged yet so you will have to pull
>> them and apply yourself.
>
> Where exactly can these be pulled from? Is there a separate git tree?
> I just built from the btrfs & btrfs-progs heads, and still do not see
> these add'l features.
Chris does not merge patches into the tree until they are
pushed to Linus. Sometimes he creates "experimental" branches
with code for testing but I don't think he has done that recently.
You can find proposed unmerged patches at:
http://patchwork.kernel.org/project/linux-btrfs/list/
jim
next prev parent reply other threads:[~2010-02-08 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 21:57 RAID-10 arrays built with btrfs & md report 2x difference in available size? 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-24 5:31 0bo0
2010-01-24 12:01 ` RK
2010-01-24 17:18 ` 0bo0
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=4B7020BF.4010302@hp.com \
--to=jowens@hp.com \
--cc=0.bugs.only.0@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rkasl@computer.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