From: NeilBrown <neilb@suse.com>
To: Patrick Dung <mpatdung@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Feature request, resumable raid check action
Date: Mon, 05 Dec 2016 11:00:39 +1100 [thread overview]
Message-ID: <87twaj5jo8.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAEtPA0CMi6PiU1VC+3h78Wnr=t-ufkT3fz=tAT0hW0jVrAp5tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
(linux-raid added back to cc:)
On Fri, Dec 02 2016, Patrick Dung wrote:
> I rebooted while it was running.
> For a new RAID, the initial sync or resync would resume after reboot.
> I thought check would have the same semantic.
>
> If I am correct, the mdcheck script is designed for a 7x24 system.
> Users can pause the 'check' action and resume later.
>
> The problem is that I could not leave my computer running on 7x24.
> A full check may take about 12 hours for a 6TB RAID1.
>
> Ok, I recheck the script and found 'sync_min'
> I can use it to manually perform resumable check action.
Correct.
You could possibly even modify mdcheck to catch SIGTERM and close down
the resync early, remembering where it is up. This might work well with
reboots.
NeilBrown
> Reference: https://www.kernel.org/doc/Documentation/md.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2016-12-05 0:00 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
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 [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=87twaj5jo8.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