From: Hugo Mills <hugo@carfax.org.uk>
To: Marc MERLIN <marc@merlins.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Any use for mkfs.btrfs -d raid5 -m raid1 ?
Date: Sun, 23 Mar 2014 22:52:29 +0000 [thread overview]
Message-ID: <20140323225229.GJ25400@carfax.org.uk> (raw)
In-Reply-To: <20140323224435.GC18293@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Sun, Mar 23, 2014 at 03:44:35PM -0700, Marc MERLIN wrote:
> If I lose 2 drives on a raid5, -m raid1 should ensure I haven't lost my
> metadate.
> From there, would I indeed have small files that would be stored entirely on
> some of the drives that didn't go missing, and therefore I could recover
> some data with 2 missing drives?
btrfs's RAID-1 is two copies only, so you may well have lost some
of your metadata. n-copies RAID-1 is coming Real Soon Now™ (Chris has
it on his todo list, along with fixing all the parity RAID stuff).
> Or is it kind of pointless/waste of space?
>
> Actually, would it make btrfs faster for metadata work since it can read
> from n drives in parallel and get data just a bit faster, or is that mostly
> negligeable?
I don't think we've got good benchmarks from anyone on any of this
kind of thing.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Great oxymorons of the world, no. 9: Standard Deviation ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-03-23 22:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 22:44 Any use for mkfs.btrfs -d raid5 -m raid1 ? Marc MERLIN
2014-03-23 22:52 ` Hugo Mills [this message]
2014-03-23 23:11 ` Marc MERLIN
2014-03-24 4:50 ` Benjamin O'Connor
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=20140323225229.GJ25400@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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