From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Understanding Default RAID Behavior
Date: Tue, 07 Feb 2012 08:25:10 +0100 [thread overview]
Message-ID: <o70709-9m4.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 4F30AF89.4090402@techsym.com
Mario Lopez <mario.lopez@techsym.com> schrieb:
> The Wiki does not make it clear as to why adding a secondary device
> defaults to RAID1 metadata and RAID0 data. I bought two SSDs with the
> intention of doing a BTRFS RAID0 for my root.
>
> What is the difference between forcing RAID0 on metadata and data as
> opposed to the default behavior? Can anyone clarify that?
I think the purpose is that on meta data corruption (which can happen and is
probably more important than file data) the file system can "heal" itself by
replacing a corrupted meta data block with an intact copy. Also during
scrubbing btrfs will check all those blocks and magically fix broken ones.
HTH
Kai
next prev parent reply other threads:[~2012-02-07 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 4:58 Understanding Default RAID Behavior Mario Lopez
2012-02-07 7:25 ` Kai Krakow [this message]
2012-02-07 10:17 ` Duncan
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=o70709-9m4.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.