All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Xiao Ni <xni@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/1] MDADM:Check mdinfo->reshape_active more times before calling Grow_continue
Date: Tue, 14 Jun 2016 14:34:09 -0400	[thread overview]
Message-ID: <wrfjbn33ei1q.fsf@redhat.com> (raw)
In-Reply-To: <1465722945-9073-1-git-send-email-xni@redhat.com> (Xiao Ni's message of "Sun, 12 Jun 2016 17:15:45 +0800")

Xiao Ni <xni@redhat.com> writes:
> Hi 
>
> When reshaping a 3 drives raid5 to 4 drives raid5, there is a chance that
> it can't start the reshape. If the disks are not enough to have spaces for
> relocating the data_offset, it needs to call start_reshape and then run 
> mdadm --grow --continue by systemd. But mdadm --grow --continue fails 
> because it checkes that info->reshape_active is 0. 
>
> The info->reshape_active is got from the superblock of underlying devices.
> Function start_reshape write reshape to /sys/../sync_action. Before writing
> latest superblock to underlying devices, mdadm --grow --continue is called.
> There is a chance info->reshape_active is 0. We should wait for superblock
> updating more time before calling Grow_continue.
>
> Regards
> Xiao

Hi Xiao,

Looks reasonable to retry before giving up.

Unfortunately your patch has some whitespace issues at the end, using
spaces instead of tabs, and lacks a signed-off-by line.

Would you mind fixing it up and resubmitting it?

Thanks,
Jes

  reply	other threads:[~2016-06-14 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-12  9:15 [PATCH 1/1] MDADM:Check mdinfo->reshape_active more times before calling Grow_continue Xiao Ni
2016-06-14 18:34 ` Jes Sorensen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-15  1:57 Xiao Ni
2016-06-15 20:27 ` Jes Sorensen
2016-06-16  1:41 Xiao Ni
2016-06-16 17:54 ` Jes Sorensen

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=wrfjbn33ei1q.fsf@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=xni@redhat.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.