From: Francis Moreau <francis.moro@gmail.com>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Force mdadm to not prompt the user
Date: Mon, 14 Apr 2014 17:33:12 +0200 [thread overview]
Message-ID: <534BFFB8.2030203@gmail.com> (raw)
Hello,
I'm using mdadm in script which setup a system automtically.
When creating a RAID array, I'd like mdadm to not prompt the user.
Currently I get:
# mdadm --create array1 --force --metadata=1.0 --level=raid1
--raid-devices=3 /dev/vdb1 /dev/vdc1 /dev/vdd1
mdadm: /dev/vdb1 appears to be part of a raid array:
level=raid0 devices=0 ctime=Thu Jan 1 01:00:00 1970
mdadm: metadata will over-write last partition on /dev/vdb1.
Continue creating array?
I thought that using --force would do the trick, but it didn't.
I'm using mdadm - v3.3 - 3rd September 2013
Is there any other way to achieve that ?
Thanks
next reply other threads:[~2014-04-14 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 15:33 Francis Moreau [this message]
2014-04-14 22:48 ` Force mdadm to not prompt the user NeilBrown
2014-04-15 6:41 ` Francis Moreau
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=534BFFB8.2030203@gmail.com \
--to=francis.moro@gmail.com \
--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 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).