From: NeilBrown <neilb@suse.de>
To: "Ryan, MichaelS (ENG Redmond)" <michaels.ryan@emc.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: raid repair checkpoint enhancement
Date: Fri, 5 Oct 2012 07:05:24 +1000 [thread overview]
Message-ID: <20121005070524.51d92d14@notabene.brown> (raw)
In-Reply-To: <A389B1DB577EF14DAA0CB1D40CF2EF5F016DF575A6@MX45A.corp.emc.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Thu, 4 Oct 2012 13:26:35 -0400 "Ryan, MichaelS (ENG Redmond)"
<michaels.ryan@emc.com> wrote:
>
> Hi all.
>
> If a device reboots during a raid repair operation ("echo repair > /sys/block/md0/md/sync_action"), the raid repair is interrupted and not restarted. For devices that are shutdown nightly, this could prevent a raid repair from ever getting to the far reaches of the array. I'd like to see an enhancement that would checkpoint the raid repair operation on shutdown similar to how a sync operation is checkpointed. Preferably, the raid repair would be restarted automatically on the next boot at the checkpoint location. Alternatively it could require user input to restart the operation at either the checkpoint location, or at the beginning.
>
> Any thoughts on this enhancement?
You can do this yourself with some scripting.
Before you shut down, record the first number in
/sys/block/mdXX/md/sync_completed
When on reboot, write that number to
/sys/block/mdXX/md/sync_min
before writing 'repair' to 'sync_action'.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-10-04 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:26 raid repair checkpoint enhancement Ryan, MichaelS (ENG Redmond)
2012-10-04 21:05 ` NeilBrown [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=20121005070524.51d92d14@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=michaels.ryan@emc.com \
/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).