From: Mario 'BitKoenig' Holbe <Mario.Holbe@TU-Ilmenau.DE>
To: linux-raid@vger.kernel.org
Subject: Re: Bug with RAID1 hot spares?
Date: Wed, 25 Oct 2006 12:41:59 +0200 [thread overview]
Message-ID: <ehnf1n$a1m$1@sea.gmane.org> (raw)
In-Reply-To: 200610242344.13576.chase.venters@clientec.com
Chase Venters <chase.venters@clientec.com> wrote:
> The main idea is to not exercise the spare as much as the other disks. All
Btw. you can also keep the spare-disk spinned down most of the time.
You should probably just make sure to spin it up from time to time to
see if it's still okay - I spin up my spares one hour per night when
smartd issues short selftests and a few more hours when smartd issues
long selftests.
regards
Mario
--
<jv> Oh well, config
<jv> one actually wonders what force in the universe is holding it
<jv> and makes it working
<Beeth> chances and accidents :)
prev parent reply other threads:[~2006-10-25 10: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
2006-10-25 4:43 ` Chase Venters
2006-10-25 10:41 ` Mario 'BitKoenig' Holbe [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='ehnf1n$a1m$1@sea.gmane.org' \
--to=mario.holbe@tu-ilmenau.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 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).