From: NeilBrown <neilb@suse.com>
To: Patrick Dung <mpatdung@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Feature request, resumable raid check action
Date: Fri, 02 Dec 2016 15:54:13 +1100 [thread overview]
Message-ID: <8737i76idm.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAEtPA0Aosn6q0pJxsh69EpHQehiSsyeyVfJf98cDhu6kORkE1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Wed, Nov 30 2016, Patrick Dung wrote:
> Hello,
>
> As I know if MD raid is using the newer metadata version, it support
> resumable raid rebuild/sync. (that is, if a server is rebooted during
> rebuild, it would resume from last position after reboot, instead of
> starting from beginning).
>
> In my recently testing (a few months ago):
> I sometimes use the mdadm 'check' action for doing the disk scrubbing
> of a MD raid.
> After I rebooted the server, the 'check' operation is forgotten and is
> not resumable.
>
> I think resumable 'check' operation is useful as the array size would
> become bigger in the future.
"check" is resumable. md doesn't record where it is up to though, you
need to do that yourself.
The "misc/mdcheck" script in the mdadm package makes use of this to
support time-limited checking, and to resume from where it left off.
You could use the script, or read it and see how it works.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2016-12-02 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 12:21 Feature request, resumable raid check action Patrick Dung
2016-12-02 4:54 ` NeilBrown [this message]
2016-12-02 5:57 ` Patrick Dung
2016-12-02 6:09 ` NeilBrown
2016-12-04 14:26 ` Mikael Abrahamsson
[not found] ` <CAEtPA0CMi6PiU1VC+3h78Wnr=t-ufkT3fz=tAT0hW0jVrAp5tQ@mail.gmail.com>
2016-12-05 0:00 ` 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=8737i76idm.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=mpatdung@gmail.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