From: Hugo Mills <hugo@carfax.org.uk>
To: Henti Smith <henti@geekware.co.za>
Cc: Leonidas Spyropoulos <artafinde@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Raid0 and drive failure.
Date: Sat, 17 Sep 2011 15:56:28 +0100 [thread overview]
Message-ID: <20110917145628.GB21530@carfax.org.uk> (raw)
In-Reply-To: <CAC_HdUrwBYgVMGiFA8dHM5X=QSksQ37iyEWSSyDipqoKKTYEsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
On Sat, Sep 17, 2011 at 04:10:44PM +0200, Henti Smith wrote:
> Hugo Mills wrote at some point:
> > I'm confused. How would you expect to recover a file on a broken
> > RAID-0 when half (or 1/3, or whatever) of the data in it has gone away
> > for good? The file is lost and gone forever. If you care somewhat
> > about your data, use RAID-1, or -10 (or -5 or -6 when they arrive in
> > btrfs[1]). If you really care about your data, keep off-machine and
> > off-site backups -- RAID is not a backup.
>
> That's just it, I don't care about my data that is lost when a drive
> fails, I care about loosing all the data when only one drive fails.
> Hence I'm trying to find out if there is a way to have fault tolerant
> drive pooling.
> After some more reading linear mode seems to offer the best options if
> you can only discard the files in the FS that islost when a drive is
> lost, but I'm still looking more into this.
>
> At it's core I'm looking for a way to do something similar windows
> drive extender that allows you to pool your drives without loosing all
> your data when one drive is lost.
Aaaah, OK. Things become clearer.
mkfs.btrfs -d single -m raid1 is probably what you want, then.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Quantum Mechanics: the dreams stuff is made of. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-09-17 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 12:25 Raid0 and drive failure Henti Smith
[not found] ` <CAAeznTp1eX8m--Mw-RFNY8VmU8O08kRNQeOmHAZo=cGNxvV7Tg@mail.gmail.com>
2011-09-16 15:06 ` Henti Smith
2011-09-16 15:10 ` Hugo Mills
2011-09-16 15:24 ` Henti Smith
2011-09-17 7:20 ` Henti Smith
2011-09-17 11:36 ` Hugo Mills
2011-09-17 14:10 ` Henti Smith
2011-09-17 14:56 ` Hugo Mills [this message]
2011-09-17 15:05 ` Roman Mamedov
2011-09-17 15:21 ` Henti Smith
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=20110917145628.GB21530@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=artafinde@gmail.com \
--cc=henti@geekware.co.za \
--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.