From: Philip Molter <philip@corp.texas.net>
To: linux-raid@vger.kernel.org
Subject: Re: Force parity resync on raid5?
Date: Thu, 12 Aug 2004 06:52:52 -0500 [thread overview]
Message-ID: <411B5A14.8070608@corp.texas.net> (raw)
In-Reply-To: <200408120406.i7C46s309087@watkins-home.com>
> Recovering from a power failure does force a re-build (2.4), but from what I
> remember the system looks like it is re-building a failed disk, which is not
> what he wants to do. If the parity was good, re-building any 1 disk would
> be fine.
Actually, under a 2.4, the superblock is marked dirty and the parity is
rebuilt. We've done this to over 100 systems (thank you, broken RedHat
installer) and it's worked flawlessly.
Neil, the new mdadm --update=resync works like a charm. The one thing I
did notice is that when a drive fails out during the resync, the resync
restarts on the remaining failed drives. As far as I can tell, that
does what it's supposed to. Is that a nice little feature of the resync?
Philip
next prev parent reply other threads:[~2004-08-12 11:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 23:10 Force parity resync on raid5? Philip Molter
2004-08-10 9:04 ` Gordon Henderson
2004-08-12 4:06 ` Guy
2004-08-12 11:52 ` Philip Molter [this message]
2004-08-12 12:31 ` David Greaves
2004-08-12 15:22 ` Guy
2004-08-12 16:26 ` David Greaves
2004-08-12 17:07 ` Philip Molter
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 12:03 Philip Molter
2004-08-10 12:39 ` Neil Brown
2004-08-10 14:30 ` Philip Molter
2004-08-11 2:28 ` Neil Brown
2004-08-11 3:37 ` Philip Molter
2004-08-11 9:23 ` David Greaves
2004-08-12 17:15 Salyzyn, Mark
2004-08-12 18:16 ` Guy
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=411B5A14.8070608@corp.texas.net \
--to=philip@corp.texas.net \
--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.