From: Lars Marowsky-Bree <lmb@suse.de>
To: "Kiniger, Karl (GE Healthcare)" <karl.kiniger@med.ge.com>,
linux-kernel@vger.kernel.org
Subject: Re: raid 1 - automatic 'repair' possible?
Date: Tue, 18 Jan 2005 22:46:05 +0100 [thread overview]
Message-ID: <20050118214605.GY22648@marowsky-bree.de> (raw)
In-Reply-To: <20050118211801.GA28400@wszip-kinigka.euro.med.ge.com>
On 2005-01-18T22:18:01, "Kiniger, Karl (GE Healthcare)" <karl.kiniger@med.ge.com> wrote:
> idea for enhancement of software raid 1:
>
> every time the raid determines that a sector cannot
> be read it could at least try to overwrite the bad are
> with good data from the other disk.
The idea is good and I'm sure we'll love to get a patch ;-)
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX Products GmbH - A Novell Business
next prev parent reply other threads:[~2005-01-18 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 21:18 raid 1 - automatic 'repair' possible? Kiniger, Karl (GE Healthcare)
2005-01-18 21:46 ` Lars Marowsky-Bree [this message]
2005-01-19 10:48 ` Kiniger
2005-01-19 11:55 ` Jakob Oestergaard
2005-01-28 16:39 ` Ric Wheeler
2005-01-31 16:01 ` Alan Cox
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=20050118214605.GY22648@marowsky-bree.de \
--to=lmb@suse.de \
--cc=karl.kiniger@med.ge.com \
--cc=linux-kernel@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