All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: Chris Dunlop <chris@onthe.net.au>,
	Chris Murphy <lists@colorremedies.com>
Cc: Brad Campbell <lists2009@fnarfbargle.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Rewrite md raid1 member
Date: Sat, 20 Aug 2016 11:44:32 +0100	[thread overview]
Message-ID: <57B83490.2040704@youngman.org.uk> (raw)
In-Reply-To: <20160820014336.GA30642@onthe.net.au>

On 20/08/16 02:43, Chris Dunlop wrote:
> Then again, I guess in the end what I'd really like is to be able to
> flag a particular disk to md for "write repair", and tell md to repair.
> Then md would read data from unflagged disks to write to the flagged
> disk (that could work for parity raids as well as mirrors).

I had that idea. I'm probably better at understanding and documenting
things, hence my interest in the raid wiki, but I'm looking at this
exact thing as a project for my first foray into kernel programming. Is
that wise? :-)

Basically, do a stripe integrity check, and optionally rewrite it? I
don't to what extent linux raid actually implements a lot of interesting
theoretical abilities, and if I can document it, I can then identify
holes and try and fill them. Especially when you're trying to recover a
broken array, the more options you have, the better ...

Unfortunately the raid wiki admin is MIA at the moment, and I really
want to hack that as a learning exercise before I start messing about
with kernel code.

Cheers,
Wol

  reply	other threads:[~2016-08-20 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  3:04 Rewrite md raid1 member Chris Dunlop
2016-08-18  3:27 ` Brad Campbell
2016-08-18  4:01   ` Chris Dunlop
2016-08-19 11:52     ` Wols Lists
2016-08-19 12:46       ` Chris Dunlop
2016-08-19 16:10         ` Chris Murphy
2016-08-20  1:43           ` Chris Dunlop
2016-08-20 10:44             ` Wols Lists [this message]
2016-08-19 21:26         ` NeilBrown
2016-08-20  1:57           ` Chris Dunlop
2016-08-20  6:52             ` NeilBrown

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=57B83490.2040704@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=chris@onthe.net.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists2009@fnarfbargle.com \
    --cc=lists@colorremedies.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.