public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: multiple device usage
Date: Mon, 29 Dec 2008 23:52:29 +1100	[thread overview]
Message-ID: <200812292352.33059.chris@csamuel.org> (raw)
In-Reply-To: <3d0408630812290433r7f2bb07cue3239c8acf958bb3@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

Hello Yan,

On Mon, 29 Dec 2008 11:33:18 pm Yan Zheng wrote:

> 2008/12/29 Chris Samuel <chris@csamuel.org>:
>
> > The rebalancing code does appear (from a naive read of the code) to be
> > able to rebalance over stripes, but I have no idea if the disk format
> > currently supports changing that on the fly.
>
> The rebalancing moves data/metadata to newly created chunks. If there
> are two devices, the new chunks will be set up as RAID-1 by default.

Very interesting!  I didn't realise that - I was presuming that the 
BTRFS_BLOCK_GROUP_RAID1 ioctl needed to be passed through (as at mkfs time) to 
change it into a RAID1 array.

Could you point me at the code where this change is detected please ?   Just 
so I can try and wrap my mind around it!

> > Again it would appear that you need to have two partitions and that btrfs
> > cannot (at present) keep multiple data stripes on the same partition.
>
> Yes. I think this is due to performance reason.

Understood.

> Changing the code to support data duplication in single spindle configuration
> is easy.

OK, that's encouraging (though for my immediate purposes creating two 
partitions is fine, but it might make life easier for others).

Again thanks so much for the response!

All the best,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 481 bytes --]

  reply	other threads:[~2008-12-29 12:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 23:15 multiple device usage devzero
2008-12-27  2:44 ` Yan Zheng
2008-12-27 14:12   ` Roland
2008-12-28 13:26     ` yanhai zhu
2008-12-29 10:49       ` Stephan von Krawczynski
2008-12-29 12:31       ` Roland
2008-12-29 12:35         ` Yan Zheng
2008-12-30 21:43           ` Chris Mason
2008-12-27  6:45 ` Chris Samuel
2008-12-29 11:32   ` Chris Samuel
2008-12-29 12:33     ` Yan Zheng
2008-12-29 12:52       ` Chris Samuel [this message]
2008-12-29 15:16         ` Yan Zheng
2008-12-30 21:25           ` Chris Mason
2009-01-01  1:02             ` Chris Samuel

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=200812292352.33059.chris@csamuel.org \
    --to=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