From: Martin Cracauer <cracauer@cons.org>
To: linux-raid@vger.kernel.org
Subject: Periodic RebuildStarted event
Date: Mon, 7 Feb 2011 18:44:11 -0500 [thread overview]
Message-ID: <20110207234411.GA93362@cons.org> (raw)
In-Reply-To: <AANLkTinwowg1evk44=46VO+Eni1B=G5Mr_X1r32GO5eF@mail.gmail.com>
I just got through the RebuildStarted event which seems to be
monthly. This is being triggered by my Debian config, but before I
nuke it I'd like to know a little more.
If a real disk error happens during this rebuild on a raid5, would the
disk go into regular degraded mode or would it count as a double
fault?
I also noticed that recently all the checks for all the arrays happen
simultaneously. That's bad because most of them share the same
physical disks. Am I imagining this or was the system smart enough to
do them one after another until recently?
Do you do period checks? I get lots of device mismatches reported but
apparently that's normal if there's write activity. The whole thing
sound contra-productive to me and might panic new users.
Martin
--
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org> http://www.cons.org/cracauer/
next prev parent reply other threads:[~2011-02-07 23:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 16:19 raid1 sector size Roberto Spadim
2011-02-06 16:49 ` Roberto Spadim
2011-02-06 18:03 ` Jérôme Poulin
2011-02-06 22:30 ` Stan Hoeppner
2011-02-07 1:21 ` Roberto Spadim
2011-02-07 23:44 ` Martin Cracauer [this message]
2011-02-07 23:52 ` Periodic RebuildStarted event Roberto Spadim
2011-02-07 23:59 ` Martin Cracauer
2011-02-08 0:28 ` Roberto Spadim
2011-02-08 0:25 ` NeilBrown
2011-03-15 3:16 ` CoolCold
2011-03-15 3:28 ` Roberto Spadim
2011-03-15 3:51 ` CoolCold
2011-03-15 4:16 ` Roberto Spadim
2011-03-15 3:41 ` NeilBrown
2011-03-15 4:21 ` CoolCold
2011-03-15 6:17 ` 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=20110207234411.GA93362@cons.org \
--to=cracauer@cons.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.