From: Robin Green <greenrd@greenrd.org>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2 and Software RAID
Date: Wed, 1 Sep 2004 16:22:34 +0100 [thread overview]
Message-ID: <20040901152234.GB4300@localhost.localdomain> (raw)
In-Reply-To: <63BAEF7DCB973A469B1A60CBE113C1650872A631@cmss-mail.Tickets.com>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
On Tue, Aug 31, 2004 at 05:44:04PM -0700, Yang, Daniel wrote:
> Finally, the combination does not support bad-block replacement mechanisms.
Bad block replacement has been implemented in hardware for years so this
is not an issue. If you get a huge number of bad blocks you should really
consider replacing the drive concerned.
--
Robin
Weblog: http://lrp.greenrd.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-01 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 0:44 [linux-lvm] LVM2 and Software RAID Yang, Daniel
2004-09-01 15:22 ` Robin Green [this message]
2004-09-01 18:00 ` [linux-lvm] LVM and Ghost James P
2004-09-01 18:21 ` Luca Berra
2004-09-01 18:33 ` rich turner
2004-09-01 18:24 ` Clint Byrum
2004-09-01 17:54 ` [linux-lvm] LVM2 and Software RAID Peter A. Castro
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=20040901152234.GB4300@localhost.localdomain \
--to=greenrd@greenrd.org \
--cc=linux-lvm@redhat.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