From: flame <flame@ivt.com.au>
To: linux-raid@vger.kernel.org
Subject: mdadm --dangerous-no-resync equivalent
Date: Thu, 10 Mar 2005 12:00:18 +1100 [thread overview]
Message-ID: <1110416418.4371.15.camel@localhost.localdomain> (raw)
Hi,
I have an installer (http://sourceforge.net/projects/terraformix/) that
creates Raid 1 arrays, previously the arrays were created with mkraid
using the --dangerous-no-resync option. I am now required to build the
arrays with mdadm and have the following questions ;
1) Is there an equivalent of --dangerous-no-resync in mdadm ?
2) Can I just go ahead and install onto a newly created RAID 1 array
without waiting for it to resync ?
3) Can I just go ahead and install onto a newly created RAID 5 array
without waiting for it to resync ?
Thanks in advance.
--
flame <flame@ivt.com.au>
next reply other threads:[~2005-03-10 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 1:00 flame [this message]
2005-03-10 1:14 ` mdadm --dangerous-no-resync equivalent Neil Brown
2005-03-10 2:54 ` Daniel Pittman
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=1110416418.4371.15.camel@localhost.localdomain \
--to=flame@ivt.com.au \
--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).