public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Ahmed Kamal <email.ahmedkamal@googlemail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: single disk reed solomon codes
Date: Mon, 04 Aug 2008 07:31:02 -0400	[thread overview]
Message-ID: <4896E876.2030507@redhat.com> (raw)
In-Reply-To: <3da3b5b40808032352t704700cbmf99245fc56bfc2bd@mail.gmail.com>

Ahmed Kamal wrote:
> 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 ?
>
>   

This is an interesting idea and could help recover from some types of 
failures (for example, single head failures) or localized bad sectors 
(think of dust or junk on the platter).  This is almost certainly a big 
win for single disk systems. 

You would probably still need to RAID (or do other protection schemes) 
to get enterprise class data availability since you clearly cannot 
handle a full drive failure whenever you have multiple drives in a system.

Thanks!

ric


  reply	other threads:[~2008-08-04 11:31 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
2008-08-04 11:31           ` Ric Wheeler [this message]
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=4896E876.2030507@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=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