From: Matthias Urlichs <matthias@urlichs.de>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Re-map disk sectors in userspace when rewriting after read errors
Date: Wed, 16 Sep 2009 15:13:33 +0200 [thread overview]
Message-ID: <1253106813.17888.9.camel@localhost> (raw)
In-Reply-To: <87ws3z5iro.fsf@frosties.localdomain>
On Wed, 2009-09-16 at 11:41 +0200, Goswin von Brederlow wrote:
> Alternatively write a re-map device-mapper target that reserves some
> space of the disk and remaps bad blocks itself.
>
That'd require some place to store the mapping so that the whole thing
still works after a reboot. Which should probably be on a different
disk.
I tend to want to move (part of) that problem to userspace; you may want
to do more than a simple remapping of a few blocks when that happens
(e.g. test-reading the surrounding area).
next prev parent reply other threads:[~2009-09-16 13:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 6:23 Re-map disk sectors in userspace when rewriting after read errors Matthias Urlichs
2009-09-15 6:45 ` 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 [this message]
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=1253106813.17888.9.camel@localhost \
--to=matthias@urlichs.de \
--cc=goswin-v-b@web.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 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.