From: "Martin K. Petersen" <mkp@mkp.net>
To: Dub <dub@latnet.lv>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Corrections for RAID1 howto and Resyncing after failure
Date: 08 Jul 2003 16:11:28 -0400 [thread overview]
Message-ID: <yq1llv8dbin.fsf@wilson.mkp.net> (raw)
In-Reply-To: <1057687402.3f0b076a99c5d@clients.latnet.lv>
>>>>> "Dub" == Dub <dub@latnet.lv> writes:
Dub> Command from FAQ: mdadm --create /dev/md0 --level 1
Dub> --raid-devices=2 missing /dev/sdb2
Dub> Command working with curreny woody release: mdadm -C /dev/md0
Dub> --level raid1 --raid-disks 2 missing /dev/sde2
Dub> There is no --raid-devices option in my release!
Odd. I'm running mdadm 1.2.0 and it says:
allegro:~# mdadm --create --help 2>&1 | grep raid-dev
Usage: mdadm --create device -chunk=X --level=Y --raid-devices=Z devices
--raid-devices= -n : number of active devices in array
Maybe Neil changed it in a later version?
Dub> I have mirrored boot, swap and root devices on pair of physical
Dub> disks. I took off one hot-plug disk and returned it back. root
Dub> device did not want to resync even after reboot.
Well. If the disk is no longer part of the metadevice, you manually
have to add it using the mdadm command.
It would be quite dangerous if the RAID code decided to add things to
an array just because a disk is inserted (fine for a storage
appliance, bad idea for a server).
CONFIG_HOTPLUG has nothing to do with it.
--
Martin K. Petersen http://mkp.net/
next prev parent reply other threads:[~2003-07-08 20:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-08 18:03 [parisc-linux] Corrections for RAID1 howto and Resyncing after failure Dub
2003-07-08 20:11 ` Martin K. Petersen [this message]
2003-07-09 8:29 ` Joel Soete
2003-07-09 12:27 ` Matthew Wilcox
2003-07-09 13:43 ` Joel Soete
2003-07-09 15:54 ` Grant Grundler
2003-07-09 15:58 ` Matthew Wilcox
2003-07-09 16:03 ` Grant Grundler
2003-07-09 13:04 ` Dub
2003-07-09 13:25 ` Joel Soete
2003-07-10 8:58 ` dub
2003-07-10 14:52 ` Joel Soete
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=yq1llv8dbin.fsf@wilson.mkp.net \
--to=mkp@mkp.net \
--cc=dub@latnet.lv \
--cc=parisc-linux@lists.parisc-linux.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