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 22:32:05 +1100	[thread overview]
Message-ID: <200812292232.08037.chris@csamuel.org> (raw)
In-Reply-To: <200812271745.45860.chris@csamuel.org>

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

On Sat, 27 Dec 2008 5:45:42 pm Chris Samuel wrote:

> I'll add two questions that're not answered by the Wiki too.. :-)

Looking at the source implies to me:

> 1) If you add a second disk to an existing btrfs filesystem, can you get it
> to set it up as a RAID-1 arrangement rather than just rebalancing the
> metadata and then striping ?

No, you can't, the data stripe numbers seem to be set at mkfs time.

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.

> 2) With the concerns that people have about SSD reliability (hi Val :-) !)
> would it make sense to set up two equal sized partitions on the SSD and use
> RAID-1 across them, or can you tell btrfs to keep multiple copies of the
> data, a la ZFS ?

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.

Could someone who actually knows the code to comment on whether my inferences 
are accurate or not please ?  :-)

cheers,
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 11:32 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 [this message]
2008-12-29 12:33     ` Yan Zheng
2008-12-29 12:52       ` Chris Samuel
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=200812292232.08037.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