From: Konstantinos Skarlatos <k.skarlatos@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
Hugo Mills <hugo@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs data dup on single device?
Date: Thu, 26 Jun 2014 01:26:17 +0300 [thread overview]
Message-ID: <53AB4C89.1060203@gmail.com> (raw)
In-Reply-To: <1403707306.4857.13.camel@heisenberg.scientia.net>
On 25/6/2014 5:41 μμ, Christoph Anton Mitterer wrote:
> On Wed, 2014-06-25 at 08:47 +0100, Hugo Mills wrote:
>> This has variously been possible and not over the last few years. I
>> think it's finally come down on the side of "not",
> I think that would really be a loss... :(
>
>
>> The question is, why?
> Well imagine you have some computer which can only have one disk drive
> (laptop, etc.) and you still want at least some kind of redundancy
> against bit rot errors.
>
>
> IMO, btrfs should support most flavours out there...
> - n-way duplicates on the same device (and not just DUP with n=2)
For the same device there is also erasure coding, where you lose lets
say 10% capacity, and have the benefit of recovering from the most
probable disk errors that dont take the whole disk with them, bad sectors.
> - n-way mirrors on multiple devices (i.e. what we have right now with
> RAID1 plus up to classic RAID1 with copies on each device
> - RAID5/6
> - n-way striped+parity with n>2
> - "stacked" layouts (RAID 10 as e.g. MD has it,... RAID50, 60)
>
>
> And terminology should really be re-worked... IMHO it's very bad to use
> the term RAID1, if it's not what classic RAID1 does.
>
>
> Cheers,
> Chris.
>
--
Konstantinos Skarlatos
next prev parent reply other threads:[~2014-06-25 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 7:25 btrfs data dup on single device? Daniel Landstedt
2014-06-25 7:47 ` Hugo Mills
2014-06-25 9:00 ` Daniel Landstedt
2014-06-25 13:33 ` Imran Geriskovan
2014-06-25 14:41 ` Christoph Anton Mitterer
2014-06-25 22:26 ` Konstantinos Skarlatos [this message]
2014-06-25 18:55 ` Chris Murphy
2014-06-26 21:13 ` Imran Geriskovan
2014-06-25 10:48 ` 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=53AB4C89.1060203@gmail.com \
--to=k.skarlatos@gmail.com \
--cc=calestyo@scientia.net \
--cc=hugo@carfax.org.uk \
--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.