linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Neil Brown <nfbrown@novell.com>,
	andras@tantosonline.com, linux-raid@vger.kernel.org
Subject: Re: How to recover after md crash during reshape?
Date: Wed, 21 Oct 2015 16:37:17 -0400	[thread overview]
Message-ID: <5627F77D.1000600@turmel.org> (raw)
In-Reply-To: <87k2qg0xz6.fsf@notabene.neil.brown.name>

On 10/21/2015 04:26 PM, Neil Brown wrote:
> Phil Turmel <philip@turmel.org> writes:

>> Hmmm.  This feature has advanced beyond my last look at the code.  I was
>> under the impression the backup option was only optional when mdadm
>> could move the data offset.  Does this new algorithm apply to v0.90
>> metadata, a v3.2 kernel, and v3.2.5 mdadm?
>>
> 
> It isn't a new algorithm, it is the original algorithm.
> 
> In mdadm-2.4-pre1 (march 2006), you couldn't specify a backup file, but
> you could grow a raid5 to more devices.
> That was changed by a patch with comment:
> 
>     Allow resize to backup to a file.
>     
>     To support resizing an array without a spare, mdadm now understands
>       --backup-file=
>     which should point to a file for storing a backup of critical data.
>     This can be given to --grow which will create the file, or
>     --assemble which will restore from the file if needed.
>     
> The backup-file was subsequently used to support in-place reshapes and
> array shrinking.

Ah, ok.  I wasn't using parity raid that far back, and never noticed
that growing to more devices worked that way.

Thanks for clarifying.

Phil


      reply	other threads:[~2015-10-21 20:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  2:35 How to recover after md crash during reshape? andras
2015-10-20 12:50 ` Anugraha Sinha
2015-10-20 13:04 ` Wols Lists
2015-10-20 13:49 ` Phil Turmel
     [not found]   ` <3baf849321d819483c5d20c005a31844@tantosonline.com>
2015-10-20 15:42     ` Phil Turmel
2015-10-20 22:34       ` Anugraha Sinha
2015-10-21  3:52       ` andras
2015-10-21 12:01         ` Phil Turmel
2015-10-21 16:17       ` Wols Lists
2015-10-21 16:05         ` Phil Turmel
2015-10-25 14:15       ` andras
2015-10-25 23:02         ` Phil Turmel
2015-10-28 16:31           ` Andras Tantos
2015-10-28 16:42             ` Phil Turmel
2015-10-28 17:10               ` Andras Tantos
2015-10-28 17:38                 ` Phil Turmel
2015-10-29 16:59               ` Andras Tantos
2015-10-30 18:12                 ` Phil Turmel
2015-11-03 23:42                   ` How to recover after md crash during reshape? - SOLVED/SUMMARY Andras Tantos
2015-10-21  1:35 ` How to recover after md crash during reshape? Neil Brown
2015-10-21  4:03   ` andras
2015-10-21 12:18   ` Phil Turmel
2015-10-21 20:26     ` Neil Brown
2015-10-21 20:37       ` Phil Turmel [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=5627F77D.1000600@turmel.org \
    --to=philip@turmel.org \
    --cc=andras@tantosonline.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=nfbrown@novell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).