All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
	ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 1/2] FIX: In Grow_restart() array parameters are wrongly used
Date: Thu, 14 Apr 2011 17:45:30 +1000	[thread overview]
Message-ID: <20110414174530.4f3bba5a@notabene.brown> (raw)
In-Reply-To: <20110411133908.4917.6842.stgit@gklab-128-013.igk.intel.com>

On Mon, 11 Apr 2011 15:39:08 +0200 Adam Kwolek <adam.kwolek@intel.com> wrote:

> Problem can be obvious visible when to 3-disks raid5 array 2 disks are added.
> (added disks number + parity == old disks number)
> Mdadm generates floating point exception and core file is generated
> due to division by 0 (odata == 0).
> 
> During restart for external metadata, getinfo_super() returns
> in mdinfo->array.raid_disks old disks number, that has to be increased
> by delta_disks to receive new value. Function getinfo_super()
> cannot return raid_disks field in different way, as array starting
> geometry information. We are still going to final array geometry.
> This Grow_restart() should have in mind and calculate local variables
> in proper way.
> 
> This change makes Grow_restart() to interpret parameters in the same way
> as reshape_array() did during reshape start, and it will do it in the same
> way when it will be called from Continue_reshape().

sorry, but I don't like this change.
I never like having different handling for 'external' and 'non-external'.
Sometimes it is obviously necessary, but we should avoid it if possible.

Once reshape has started, 'raid_disks' is the new number of disks, not the
old number.

So sysfs_set_array should be changed to set raid_disks to
    raid_disk - delta_disks
in the first instance, then if reshape is active, to raid_disks.

And getinfo_super should return the 'new' number of disks.

And reshape_array might need to fiddle with raid_disks before calling 
analyse_change in the reshape_active case.

So it is more changes, but I think it is a better result.

Thanks,
NeilBrown

> 
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
> 
>  Grow.c |   12 ++++++++----
>  1 files changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/Grow.c b/Grow.c
> index d4308bc..1fdee7e 100644
> --- a/Grow.c
> +++ b/Grow.c
> @@ -3102,13 +3102,17 @@ int Grow_restart(struct supertype *st, struct mdinfo *info, int *fdlist, int cnt
>  	unsigned long long  nstripe, ostripe;
>  	int ndata, odata;
>  
> -	odata = info->array.raid_disks - info->delta_disks - 1;
> +	if (st->ss->external) {
> +		old_disks = info->array.raid_disks;
> +		ndata = info->array.raid_disks + info->delta_disks - 1;
> +	} else {
> +		old_disks = info->array.raid_disks - info->delta_disks;
> +		ndata = info->array.raid_disks - 1;
> +	}
> +	odata = old_disks - 1;
>  	if (info->array.level == 6) odata--; /* number of data disks */
> -	ndata = info->array.raid_disks - 1;
>  	if (info->new_level == 6) ndata--;
>  
> -	old_disks = info->array.raid_disks - info->delta_disks;
> -
>  	if (info->delta_disks <= 0)
>  		/* Didn't grow, so the backup file must have
>  		 * been used


      parent reply	other threads:[~2011-04-14  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 13:39 [PATCH 1/2] FIX: In Grow_restart() array parameters are wrongly used Adam Kwolek
2011-04-11 13:39 ` [PATCH 2/2] FIX: Set reshape parameters for all disks belongs to new array geometry Adam Kwolek
2011-04-14  7:45 ` 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=20110414174530.4f3bba5a@notabene.brown \
    --to=neilb@suse.de \
    --cc=adam.kwolek@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=wojciech.neubauer@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 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.