linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francis Moreau <francis.moro@gmail.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: Force mdadm to not prompt the user
Date: Tue, 15 Apr 2014 08:41:44 +0200	[thread overview]
Message-ID: <534CD4A8.6030205@gmail.com> (raw)
In-Reply-To: <20140415084830.1cbf299c@notabene.brown>

On 04/15/2014 12:48 AM, NeilBrown wrote:
> On Mon, 14 Apr 2014 17:33:12 +0200 Francis Moreau <francis.moro@gmail.com>
> wrote:
> 
>> 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 ?
> 
> run
>    man mdadm
> 
> search for "prompt".... doesn't find anything.
> search for "ask".  Ahh, there is the answer.
> 

ah, sorry I missed it.

In the meantime I tried the --zero-superblock in order to clean the
metadata from /dev/vdb1:

# 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? n
mdadm: create aborted.

# mdadm --zero-superblock /dev/vdb1
mdadm: Unrecognised md component device - /dev/vdb1

# mdadm --zero-superblock --force /dev/vdb1
mdadm: Unrecognised md component device - /dev/vdb1

# 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? n

mdadm doesn't tell me which metadata it sees but I tried the different
ones and got the same result.

What am I missing ?

Thanks.


      reply	other threads:[~2014-04-15  6:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 15:33 Force mdadm to not prompt the user Francis Moreau
2014-04-14 22:48 ` NeilBrown
2014-04-15  6:41   ` Francis Moreau [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=534CD4A8.6030205@gmail.com \
    --to=francis.moro@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;
as well as URLs for NNTP newsgroup(s).