From: Calvin Walton <calvin.walton@kepstin.ca>
To: "Björn Wüst" <Bjoern.Wuest@iteratec.de>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Preparing single-disk setup for future multi-disk usage
Date: Thu, 24 May 2012 06:41:27 -0400 [thread overview]
Message-ID: <1337856087.3958.5.camel@ayu> (raw)
In-Reply-To: <5A83377DACA90F4896A338250D088E8F14B35F09@HMEXMBCLUS01.ci04.de>
On Thu, 2012-05-24 at 08:05 +0200, Björn Wüst wrote:
> Good morning,
>
>
> I currently have a single-disk setup where I want to use btrfs
> filesystem. Yet, I expect to add additional disks to this system in
> the future. Those disks shall be visible to the OS like a single disk,
> i.e. using multi-disk feature in btrfs. While data shall be striped
> among those disks in the future, meta data shall be mirrored for
> better fault tolerance (loss of some data is acceptable, while loss of
> all data is not acceptable).
If you're using the "RAID 0" (striping) mode, you will not be able to
recover any data in a useful form after a disk failure, because each
file will have been broken into small chunks and spread over both disks.
If you use the 'single' allocation mode instead, it is more likely that
individual files will be mostly on one disk, but there are no
guarantees.
If you want data to be recoverable, you should use a redundant raid
mode; otherwise don't expect that you'll be able to save much after a
disk failure.
--
Calvin Walton <calvin.walton@kepstin.ca>
prev parent reply other threads:[~2012-05-24 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 6:05 Preparing single-disk setup for future multi-disk usage Björn Wüst
2012-05-24 6:18 ` Fajar A. Nugraha
2012-05-24 8:40 ` Hugo Mills
2012-05-24 10:20 ` Bjoern Wuest
2012-05-24 10:41 ` Calvin Walton [this message]
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=1337856087.3958.5.camel@ayu \
--to=calvin.walton@kepstin.ca \
--cc=Bjoern.Wuest@iteratec.de \
--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;
as well as URLs for NNTP newsgroup(s).