linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: linux-raid@vger.kernel.org
Subject: Re-map disk sectors in userspace when rewriting after read errors
Date: Tue, 15 Sep 2009 06:23:33 +0000 (UTC)	[thread overview]
Message-ID: <h8nbt5$n8p$1@ger.gmane.org> (raw)

Hi,

my problem is that I have a bunch of crappy disks which seem unable to
reliably remap bad areas after a read error.

This obviously makes the read error rewrite feature of our beloved 
RAID5/6 code somewhat less than useful.

What I would like to do is to re-map these sectors in userspace -- either 
by browbeating the disk into it, or by using the Device Mapper. So I'd 
need a way to tell a userspace daemon "this device+block is unreadable", 
and wait until said daemon tells the RAID core to go ahead.

I can do the userspace side easily, but my time to dig through the RAID 
code and implement that sort of channel in a maintainable way is somewhat 
limited. (Plus, I need that code sooner rather than later.)

Would somebody be able to help out? There may be some money in it ...

-- 
Matthias Urlichs


             reply	other threads:[~2009-09-15  6:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  6:23 Matthias Urlichs [this message]
2009-09-15  6:45 ` Re-map disk sectors in userspace when rewriting after read errors berk walker
2009-09-15  7:23   ` Matthias Urlichs
2009-09-15  7:13 ` Alex Butcher
2009-09-15  7:29   ` Matthias Urlichs
2009-09-15  7:37     ` Alex Butcher
2009-09-15 10:48       ` Matthias Urlichs
2009-09-16  9:41         ` Goswin von Brederlow
2009-09-16 13:13           ` Matthias Urlichs
2009-09-18  8:17             ` Majed B.
2009-09-18  8:28               ` Robin Hill
2009-09-18  9:57                 ` Majed B.
2009-09-18 10:22                   ` Robin Hill
2009-09-18 10:52                     ` Majed B.
2009-09-18 11:15                       ` Robin Hill
2009-09-18 11:35               ` Matthias Urlichs
2009-09-18 17:44                 ` John Robinson
2009-09-18 18:02                   ` Greg Freemyer
2009-09-18 20:13                     ` Majed B.
2009-10-02 13:55                       ` Bill Davidsen
2009-09-15 10:40 ` Majed B.
2009-09-15 10:52   ` Matthias Urlichs
2009-09-15 11:03     ` Majed B.
2009-09-15 17:02       ` Majed B.
2009-09-15 18:05         ` Matthias Urlichs
2009-09-15 18:14           ` Majed B.
2009-09-15 18:44             ` Matthias Urlichs
2009-09-16  9:31               ` Majed B.
2009-09-16  9:44                 ` Matthias Urlichs
2009-09-16  9:52                   ` Majed B.
2009-09-16 13:05                     ` Alex Butcher
2009-09-16 10:00                   ` Robin Hill
2009-09-16 10:07                     ` Majed B.

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='h8nbt5$n8p$1@ger.gmane.org' \
    --to=matthias@urlichs.de \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).