Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Ram Ramesh <rramesh2400@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: mdadm --grow with --backup-file does not create backupfile?
Date: Sun, 12 Oct 2014 20:49:21 -0500	[thread overview]
Message-ID: <543B2FA1.4030106@gmail.com> (raw)
In-Reply-To: <20141013123914.04b960ed@notabene.brown>

Good to know. Thanks.

Ramesh

On 10/12/2014 08:39 PM, NeilBrown wrote:
> On Sun, 12 Oct 2014 20:26:05 -0500 Ram Ramesh <rramesh2400@gmail.com> wrote:
>
>> I added a new disk and grew my raid6 md0 with the following command line
>>
>>      sudo mdadm --grow --raid-devices=5
>>      --backup-file=/root/grow_md0.bkp_file --layout=normalise /dev/md0
>>
>> I got a response that stated that mdadm needed to backup 384K of data.
>> However, when I checked after about 5min there was no backup file. Is
>> this expected?
> Yes.
>
> When increasing the size of an array, the backup file is needed  for a tiny
> fraction of a second at the start.
> When decreasing the size it is needed  for a tiny fraction if a second at the
> end.
> When the size isn't changed it is needed for the entire time.
>
> ... unless you have a new kernel and a new mdadm, and then the backup file
> isn't needed.
>
> NeilBrown
>
>
>
>>      386 > sudo ls /root
>>      <no files. so no output>
>>      387 > sudo ls /root/grow_md0.bkp_file
>>      ls: cannot access /root/grow_md0.bkp_file: No such file or directory
>>
>> Ramesh
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2014-10-13  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  1:26 mdadm --grow with --backup-file does not create backupfile? Ram Ramesh
2014-10-13  1:39 ` NeilBrown
2014-10-13  1:49   ` Ram Ramesh [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=543B2FA1.4030106@gmail.com \
    --to=rramesh2400@gmail.com \
    --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