Re: [PATCH 007 of 13] md: Core of raid5 resize process

On Thursday March 16, [email protected] wrote:
> NeilBrown <[email protected]> wrote:
> >
> > @@ -4539,7 +4543,9 @@ static void md_do_sync(mddev_t *mddev)
> >   		 */
> >   		max_sectors = mddev->resync_max_sectors;
> >   		mddev->resync_mismatches = 0;
> >  -	} else
> >  +	} else if (test_bit(MD_RECOVERY_RESHAPE, &mddev->recovery))
> >  +		max_sectors = mddev->size << 1;
> >  +	else
> >   		/* recovery follows the physical size of devices */
> >   		max_sectors = mddev->size << 1;
> >   
> 
> This change is a no-op.   Intentional?

Uhmm... sort of.
A later patch adds stuff to the later branch but not the middle one.
This comes from creating a patch to fix a bug, then merging it back
into the wrong original patch...

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 000 of 13] md: Introduction
    • From: NeilBrown <[email protected]>
  • [PATCH 007 of 13] md: Core of raid5 resize process
    • From: NeilBrown <[email protected]>
  • Re: [PATCH 007 of 13] md: Core of raid5 resize process
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: 2.6.16-rc5: known regressions [TP 600X S3, vanilla DSDT]
• Next by Date: [PATCH 003 of 6] md: Remove an unused variable.
• Previous by thread: Re: [PATCH 007 of 13] md: Core of raid5 resize process
• Next by thread: [PATCH 013 of 13] md: Support suspending of IO to regions of an md array.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]