Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: NeilBrown <neilb@suse.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: Chunk size change stop/restart
Date: Wed, 18 Dec 2013 19:31:09 +0100	[thread overview]
Message-ID: <20131218183109.GA4670@lazy.lzy> (raw)
In-Reply-To: <20131218093210.46a208a2@notabene.brown>

On Wed, Dec 18, 2013 at 09:32:10AM +1100, NeilBrown wrote:
> On Tue, 17 Dec 2013 20:00:19 +0100 Piergiorgio Sartor
> <piergiorgio.sartor@nexgo.de> wrote:
> 
> > Hi all,
> > 
> > I started the process of changing the chunk
> > size of a RAID-5 array (5 HDDs).
> > 
> > Unfortunately, I unwisely choose a quite slow
> > device for the backup file.
> > 
> > Is it possible, without stopping the array, to
> > stop the "reshape", move the backup file to a
> > faster place and restart the process?
> 
> You might be able to kill the mdadm which over-sees the reshape, move the
> file, then use --grow --continue to continue the reshape.
> But I've never tested this and suspect that something would go wrong.

Hi Neil,

thanks for the answer.

Actually, I've another card to play.
The array is empty in the second half, so I could
try to kill mdadm (which signal? I guess the normal
kill should do) and then restart the reshape, as
soon as the 50% mark is reached.

Assuming something goes wrong, is there a way to
re-start the array forcing (maybe?) the 64k chunk
size (then a repair should simply fix the second
half, I guess).
 
> Stopping, moving, and re-assembling should work.
> 
> Being patient also works,  but can be very difficult.

That was plan A, but I missed by 1 day... :-)

bye,

-- 

piergiorgio

      reply	other threads:[~2013-12-18 18:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 19:00 Chunk size change stop/restart Piergiorgio Sartor
2013-12-17 22:32 ` NeilBrown
2013-12-18 18:31   ` Piergiorgio Sartor [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=20131218183109.GA4670@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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