From: Stephen Walton <stephen.walton@csun.edu>
To: linux-raid@vger.kernel.org
Subject: convert legacy array in place?
Date: Sun, 14 Aug 2005 14:40:12 -0700 [thread overview]
Message-ID: <42FFBA3C.1010102@csun.edu> (raw)
Hi,
It seems like this should be a FAQ but careful google and mailing list
archive searches didn't seem to turn up anything.
I have two machines with legacy RAID-0 arrays created with raidtools. I
have updated one to Fedora Core 4 and now use mdadm. Am I correct in
thinking I have to use "mdadm --build" every boot to access the array?
My mdadm.conf contains
DEVICES /dev/hda1 /dev/hdb1 /dev/hdc1
ARRAY /dev/md0 level=raid0 num-devices=3
devices=/dev/hda1,/dev/hdb1,/dev/hdc1
but the array doesn't seem to come up by itself on boot.
On the same lines, can this array be converted to a new style array just
by writing new superblocks, or do I have to do the
backup-reformat-restore thing?
TIA.
next reply other threads:[~2005-08-14 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 21:40 Stephen Walton [this message]
2005-08-15 4:29 ` convert legacy array in place? Neil Brown
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=42FFBA3C.1010102@csun.edu \
--to=stephen.walton@csun.edu \
--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).