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: Fri, 16 Sep 2011 16:10:44 +0100 [thread overview]
Message-ID: <20110916151044.GF11031@carfax.org.uk> (raw)
In-Reply-To: <CAC_HdUrh+LhBfHTMKE8VTkuwEgJbcX2mBP3pJFYivk228-VctA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
On Fri, Sep 16, 2011 at 05:06:03PM +0200, Henti Smith wrote:
> On Fri, Sep 16, 2011 at 4:49 PM, Leonidas Spyropoulos
> <artafinde@gmail.com> wrote:
> > On Sep 16, 2011 1:25 PM, "Henti Smith" <henti@geekware.co.za> wrote:
> >> This is likely a newbie question, but I just need to confirm. If you
> >> have 3 x 100GB drives in RAID0 and one drive dies this will result in
> >> total data loss correct?
> >>
> > Yes the data are lost. Read more on how raid 0 works.
>
> I have read on how raid 0 works, I was merely asking about the
> implementation of raid0 on btrfs.
>
> >> Is there no way to loose only the data that resides (even partly) on
> >> the missing drive but retain the rest of the data ?
>
> This is the more pertinent question, which it seem btrfs can't do currently.
btrfs stripes its RAID-0 data across all available disks, so you'd
lose approximately 1/3 of the data for each file. In some cases, you
might get lucky and have a small file that resides entirely on the two
undamaged disks. In that case, it *might* be possible to recover your
data, but I think in general the amount of effort involved to get that
degree of recovery is probably far outweighted by the use of your
backups to restore all of the missing data...
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
--- "Are you the man who rules the Universe?" "Well, I ---
try not to."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-09-16 15:10 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 [this message]
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
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=20110916151044.GF11031@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.