From: Brad Campbell <brad@wasp.net.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: Rebuild after catastrophic event?
Date: Sat, 08 Jan 2005 19:08:44 +0400 [thread overview]
Message-ID: <41DFF77C.8070108@wasp.net.au> (raw)
G'day all,
With 2.4 kernels I recall that md would resync an array after a catastrophic event (like a power
failure or kernel oops/panic). 2.6 does not seem to do that and just merrily fires up the array and
continues on its way. Is there a reason for the change in behaviour?
I'm wondering if I should force a resync with mdadm after such an event?
I know it used to resync, and the server at work (running 2.4.26) certainly does on next powerup.
The only other change is I recall I used to have md autodetect the arrays on startup, and now I use
mdadm to start them, but that should not matter. (should it?)
Regards,
Brad (who came home to find a paniced box and thus must ask the question)
reply other threads:[~2005-01-08 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41DFF77C.8070108@wasp.net.au \
--to=brad@wasp.net.au \
--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.