From: Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
To: linux-raid@vger.kernel.org
Subject: Timeout until degrade of RAID5 array
Date: Sun, 7 Jun 2009 21:19:22 +0200 [thread overview]
Message-ID: <200906072119.22807.gabriel_ambuehl@buz.ch> (raw)
Dear List
Apologies if this is a FAQ but googling for an hour did not yield much of a
result.
My situation:
I have a NAS running 4 WD greenpower drives in RAID5. This works all nice and
dandy, but since I do not actually need the NAS 90% of the time, I figured I
would allow the drives to spin down to save on both power, noise and heat
budget.
This works most of the times, but I've seen a few cases by now where one drive
was kicked out of the array upon wake up. My assumption is the drive took a
little too long to wake up and hence hit some form of a time out especially
because I could easily rebuild the array with the same drive.
So Is there any way to increase the time that md would wait until removing a
drive from an array?
Thanks for your time and kind regards,
Gabriel
next reply other threads:[~2009-06-07 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 19:19 Gabriel Ambuehl [this message]
2009-06-07 22:57 ` Timeout until degrade of RAID5 array NeilBrown
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=200906072119.22807.gabriel_ambuehl@buz.ch \
--to=gabriel_ambuehl@buz.ch \
--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