All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: mostafa kishani <mostafa.kishani@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Implementing Global Parity Codes
Date: Sat, 27 Jan 2018 08:37:23 +0000	[thread overview]
Message-ID: <5A6C3A43.6030701@youngman.org.uk> (raw)
In-Reply-To: <CACm9mdUJLczo8zSB5UfU9Fd_6VK3+sGCYJYdaEaX0qW1cMLtYA@mail.gmail.com>

On 27/01/18 05:47, mostafa kishani wrote:
> Dear All,
> 
> I am going to make some modifications to RAID protocol to make it more
> reliable for my case (for a scientific, and maybe later, industrial
> purpose). For example, I'm going to hold a Global Parity (a parity
> taken across the whole data stripe rather than a row)

Except that what do you mean by "row"? Aren't you using it as just
another word for "stripe"?

 alongside normal
> row-wise parities, to cope with an extra sector/page failure per
> stripe. Do you have any suggestion how can I implement this with a
> moderate effort (I mean what functions should be modified)? have any
> of you had any similar effort?

If I understand you correctly, that's easy. Raid-5 has one parity block
per stripe, enabling it to recover from one lost disk. Raid-6 has two
parity stripes, enabling it to recover from two lost disks, or one
random corrupted block.

Nobody's tried to do it, but it's a simple extension of the current
setup ... why don't you implement what I call "raid-6+", where you can
have as many parity disks as you like - in your case three. You'd need
to take the current raid-6 code and extend it - ignore raid-5 because
while the principle is the same, the detail is much simpler and cannot
be extended.

> I also appreciate if you guide me how can I enable DEBUG mode in mdadm.
> 
Can't help there, I'm afraid.

Cheers,
Wol


  reply	other threads:[~2018-01-27  8:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  5:47 Implementing Global Parity Codes mostafa kishani
2018-01-27  8:37 ` Wols Lists [this message]
2018-01-27 14:29   ` mostafa kishani
2018-01-27 15:13     ` Wols Lists
2018-01-28 13:00       ` mostafa kishani
2018-01-29 10:22       ` David Brown
2018-01-29 17:44         ` Wols Lists
2018-01-30 11:47           ` David Brown
2018-01-30 14:18           ` Brad Campbell
2018-01-30 11:30         ` mostafa kishani
2018-01-30 15:14           ` David Brown
2018-01-31 16:03             ` mostafa kishani
2018-01-31 17:53               ` Piergiorgio Sartor
2018-02-02  5:24 ` NeilBrown
2018-02-03  6:01   ` mostafa kishani

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=5A6C3A43.6030701@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=mostafa.kishani@gmail.com \
    /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.