public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ahmed Kamal" <email.ahmedkamal@googlemail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: single disk reed solomon codes
Date: Mon, 4 Aug 2008 09:52:50 +0300	[thread overview]
Message-ID: <3da3b5b40808032352t704700cbmf99245fc56bfc2bd@mail.gmail.com> (raw)
In-Reply-To: <7fe698080807210803h3a634eddw49be677e235c1c88@mail.gmail.com>

An experiment of applying RS codes for protecting data, worth a look
http://ttsiodras.googlepages.com/rsbep.html

He overwrites a series of 127 sectors and still manages to correctly
recover his data. We all know disks give us unreadable sectors every
now and then, so at least on workstations/laptops this could really be
useful ?

Advantage over single-disk-raid1 is storage efficiency (4.2MB becomes
5.2MB), that means we get 80% of useable disk space, instead of 50% if
I decide to raid1 everything ?

On Mon, Jul 21, 2008 at 6:03 PM, Dongjun Shin <djshin90@gmail.com> wrote:
> On Mon, Jul 21, 2008 at 4:40 PM, Ahmed Kamal
> <email.ahmedkamal@googlemail.com> wrote:
>> I definitely hope btrfs has this per-object "copies" property too.
>> However, simply replicating the whole contents of a directory, wastes
>> too much disk space, as opposed to RS codes
>>
>
> Although adding redundancy mechanism will help increasing the integrity of data,
> I'm not sure whether repeating the same kind of mechanism twice will help.
> (AFAIK, RS is common in HDD and BCH is common in flash due to their own
> physical characteristics)
>
> I think it is better to have another redundancy mechanism (like RAID1)
> which is independent of the algorithm used by the underlying storage.
>
> --
> Dongjun
>

  reply	other threads:[~2008-08-04  6:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-19 12:21 single disk reed solomon codes Ahmed Kamal
2008-07-19 15:18 ` Gerald Nowitzky
2008-07-19 22:15   ` Joe Peterson
2008-07-20  1:21     ` Bron Gondwana
2008-07-21  6:48   ` Tomasz Torcz
2008-07-21  7:40     ` Ahmed Kamal
2008-07-21 13:03       ` Chris Mason
2008-07-21 15:03       ` Dongjun Shin
2008-08-04  6:52         ` Ahmed Kamal [this message]
2008-08-04 11:31           ` Ric Wheeler
2008-07-19 16:50 ` David Woodhouse
2008-07-19 16:53   ` Ahmed Kamal
2008-07-21 13:05   ` Chris Mason

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=3da3b5b40808032352t704700cbmf99245fc56bfc2bd@mail.gmail.com \
    --to=email.ahmedkamal@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox