On Wed, 3 Jun 2015 15:48:40 -0700
Shaohua Li <shli@xxxxxx> wrote:
> If cache support is enabled, don't allow resize/reshape in current
> stage. In the future, we can flush all data from cache to raid before
> resize/reshape and then allow resize/reshape.
>
> Signed-off-by: Shaohua Li <shli@xxxxxx>
> ---
> drivers/md/raid5.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
> index 26561d8..29f49c7 100644
> --- a/drivers/md/raid5.c
> +++ b/drivers/md/raid5.c
> @@ -7207,6 +7207,10 @@ static int raid5_resize(struct mddev *mddev, sector_t sectors)
> * worth it.
> */
> sector_t newsize;
> + struct r5conf *conf = mddev->private;
> +
> + if (conf->cache)
> + return -EINVAL;
> sectors &= ~((sector_t)mddev->chunk_sectors - 1);
> newsize = raid5_size(mddev, sectors, mddev->raid_disks);
> if (mddev->external_size &&
> @@ -7258,6 +7262,8 @@ static int check_reshape(struct mddev *mddev)
> {
> struct r5conf *conf = mddev->private;
>
> + if (conf->cache)
> + return -EINVAL;
> if (mddev->delta_disks == 0 &&
> mddev->new_layout == mddev->layout &&
> mddev->new_chunk_sectors == mddev->chunk_sectors)
This patch should come before that patch which enables caches - the
could should be correct at each point in the series.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
