mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Ric Wheeler <ric@emc.com>
Cc: Jakob Oestergaard <jakob@unthought.net>,
	Kiniger <karl.kiniger@med.ge.com>,
	Lars Marowsky-Bree <lmb@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: raid 1 - automatic 'repair' possible?
Date: Mon, 31 Jan 2005 16:01:31 +0000	[thread overview]
Message-ID: <1107171389.14787.73.camel@localhost.localdomain> (raw)
In-Reply-To: <41FA6ADE.4010209@emc.com>


> Depending on the type of drive error, the act of writing is likely to 
> clean the questionable sector and leave you with a perfectly fine disk.
> 

Definitely - and in fact some of the other Linux tools already know
about this and do it (for example ext3 fsck will force rewrite bad
blocks if you want).


      reply	other threads:[~2005-01-31 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-18 21:18 Kiniger, Karl (GE Healthcare)
2005-01-18 21:46 ` Lars Marowsky-Bree
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 [this message]

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=1107171389.14787.73.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=jakob@unthought.net \
    --cc=karl.kiniger@med.ge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmb@suse.de \
    --cc=ric@emc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome