From: NeilBrown <neilb@suse.de>
To: Pawel Baldysiak <pawel.baldysiak@intel.com>
Cc: linux-raid@vger.kernel.org, lukasz.dorau@intel.com
Subject: Re: [PATCH] imsm: fix checking completion of RAID10 resync
Date: Wed, 31 Jul 2013 09:22:40 +1000 [thread overview]
Message-ID: <20130731092240.3230bf7f@notabene.brown> (raw)
In-Reply-To: <20130730135925.30168.91570.stgit@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 3404 bytes --]
On Tue, 30 Jul 2013 15:59:25 +0200 Pawel Baldysiak
<pawel.baldysiak@intel.com> wrote:
> If one creates RAID10 with IMSM metadata the is_resync_complete
> function returns '1' just when initial resync reaches 50%
>
> IMSM version of the is_resync_complete function has been added
> that handles the case of IMSM RAID10 correctly.
>
>
> Signed-off-by: Pawel Baldysiak <pawel.baldysiak@intel.com>
> ---
> super-intel.c | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/super-intel.c b/super-intel.c
> index 4df33f4..0371713 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -1021,6 +1021,22 @@ static int is_failed(struct imsm_disk *disk)
> return (disk->status & FAILED_DISK) == FAILED_DISK;
> }
>
> +/* IMSM version of is_resync_complete helper routine
> + * to determine resync completion
> + * since MaxSector is a moving target
> + */
> +static int imsm_is_resync_complete(struct mdinfo *array)
> +{
> + if (array->array.level != 10) {
> + if (array->resync_start >= array->component_size)
> + return 1;
> + } else {
> + if (array->resync_start >= 2*array->component_size)
> + return 1;
> + }
> + return 0;
> +}
> +
> /* try to determine how much space is reserved for metadata from
> * the last get_extents() entry on the smallest active disk,
> * otherwise fallback to the default
> @@ -7119,12 +7135,12 @@ static int imsm_set_array_state(struct active_array *a, int consistent)
> handle_missing(super, dev);
>
> if (consistent == 2 &&
> - (!is_resync_complete(&a->info) ||
> + (!imsm_is_resync_complete(&a->info) ||
> map_state != IMSM_T_STATE_NORMAL ||
> dev->vol.migr_state))
> consistent = 0;
>
> - if (is_resync_complete(&a->info)) {
> + if (imsm_is_resync_complete(&a->info)) {
> /* complete intialization / resync,
> * recovery and interrupted recovery is completed in
> * ->set_disk
Thanks.
However the bug is not specific to intel, so should be fixed in common code.
And "2*" is not really very general.
The following patch should fix it properly. If you can confirm that it fixes
the problem for you I would appreciate it.
Thanks,
NeilBrown
From 71d68ff62f945254240575cd836f5f2a09ced5d2 Mon Sep 17 00:00:00 2001
From: NeilBrown <neilb@suse.de>
Date: Wed, 31 Jul 2013 09:18:57 +1000
Subject: [PATCH] Fix is_resync_complete for RAID10
For RAID10, 'sync' numbers go up to the array size rather than the
component size. is_resync_complete() needs to allow for this.
Reported-by: Pawel Baldysiak <pawel.baldysiak@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>
diff --git a/mdmon.h b/mdmon.h
index 60fda38..5a8e120 100644
--- a/mdmon.h
+++ b/mdmon.h
@@ -91,7 +91,21 @@ extern int monitor_loop_cnt;
*/
static inline int is_resync_complete(struct mdinfo *array)
{
- if (array->resync_start >= array->component_size)
- return 1;
- return 0;
+ unsigned long long sync_size = 0;
+ int ncopies, l;
+ switch(array->array.level) {
+ case 1:
+ case 4:
+ case 5:
+ case 6:
+ sync_size = array->component_size;
+ break;
+ case 10:
+ l = array->array.layout;
+ ncopies = (l & 0xff) * ((l >> 8) && 0xff);
+ sync_size = array->component_size * array->array.raid_disks;
+ sync_size /= ncopies;
+ break;
+ }
+ return array->resync_start >= sync_size;
}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-07-30 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 13:59 [PATCH] imsm: fix checking completion of RAID10 resync Pawel Baldysiak
2013-07-30 23:22 ` NeilBrown [this message]
2013-08-01 8:46 ` Dorau, Lukasz
2013-08-01 12:32 ` Dorau, Lukasz
2013-08-05 5:43 ` 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=20130731092240.3230bf7f@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=pawel.baldysiak@intel.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).