From: Bill Davidsen <davidsen@tmr.com>
To: Chase Venters <chase.venters@clientec.com>
Cc: linux-raid@vger.kernel.org, jason.meinzer@gmail.com
Subject: Re: Bug with RAID1 hot spares?
Date: Tue, 24 Oct 2006 21:41:24 -0400 [thread overview]
Message-ID: <453EC0C4.2040006@tmr.com> (raw)
In-Reply-To: <200610202046.43033.chase.venters@clientec.com>
Chase Venters wrote:
>Greetings,
> I was just testing a server I was about to send into production on kernel
>2.6.18.1. The server has three SCSI disks with "md1" set to a RAID1 with 2
>mirrors and 1 spare.
>
I have to ask, why? If the array is mostly written you might save a bit
of bus time, but for reads having another copy of the data to read
(usually) helps the performance by reducing wait for read occurences.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-10-25 1:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 1:46 Bug with RAID1 hot spares? Chase Venters
2006-10-23 4:13 ` Neil Brown
2006-10-25 1:41 ` Bill Davidsen [this message]
2006-10-25 4:43 ` Chase Venters
2006-10-25 10:41 ` Mario 'BitKoenig' Holbe
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=453EC0C4.2040006@tmr.com \
--to=davidsen@tmr.com \
--cc=chase.venters@clientec.com \
--cc=jason.meinzer@gmail.com \
--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).