From: EJ Vincent <ej@ejane.org>
To: linux-raid@vger.kernel.org
Subject: Functioning of --backup-file prior to array growth.
Date: Mon, 25 Feb 2013 23:09:18 -0500 [thread overview]
Message-ID: <512C356E.6070803@ejane.org> (raw)
Greetings,
I didn't want to hijack Kevin's "Damage when growing RAID 5 array"
thread, but this got me thinking about my past experiences.
I'm preparing to add a disk to an existing RAID6.
In the past (more than one occasion) I've specified:
"--backup-file=/disk/not/part/of/array/md.bak" and then, after starting
the growth, I've gone to this path, and seen nothing created.
Is this a file that is created *only* in the event of an error /
failure? Should some data be written to this .bak file immediately? If
not, what could be preventing this file from being created?
Thanks for your input.
-EJ
next reply other threads:[~2013-02-26 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 4:09 EJ Vincent [this message]
2013-02-26 8:07 ` Functioning of --backup-file prior to array growth Keith Keller
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=512C356E.6070803@ejane.org \
--to=ej@ejane.org \
--cc=linux-raid@vger.kernel.org \
/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.