From: NeilBrown <neilb@suse.de>
To: John Drescher <drescherjm@gmail.com>
Cc: lilofile <lilofile@aliyun.com>, stan <stan@hardwarefreak.com>,
Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: raid5 Unplug the disk
Date: Thu, 5 Feb 2015 16:03:04 +1100 [thread overview]
Message-ID: <20150205160304.1119bb06@notabene.brown> (raw)
In-Reply-To: <CAEhu1-4krpTbF-0mLdgoTKrkdrWo8J2k80BC0t48rv3WkG3UBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
On Wed, 28 Jan 2015 11:59:30 -0500 John Drescher <drescherjm@gmail.com> wrote:
> On Wed, Jan 28, 2015 at 1:44 AM, lilofile <lilofile@aliyun.com> wrote:
> > kernel linux 3.10, centos
> > when I use 5 disk to create raid5,after sync complete, I unplug a disk,and wait a moment, then replug the same disk.
> >
> > the original 4 disk are still a raid5 which is degraded.
> > I find the single disk become a new raid5,but inactive,what the reason?
>
> stop whatever new array that shows up then use
>
> mdadm --manage /dev/mymddevice --re-add /dev/disk5
>
Also, you probably need a newer version of mdadm. Creating a new inactive
raid5 was a bug.
If you have udev configured to run "mdadm -I" on newly added devices (which I
think most distros do), then adding
POLICY action=re-add
to /etc/mdadm.conf should cause the device to automatically be added back to
the array when you plug it in.
NeilBrown
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-02-05 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 6:44 raid5 Unplug the disk lilofile
2015-01-28 16:59 ` John Drescher
2015-02-05 5:03 ` NeilBrown [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=20150205160304.1119bb06@notabene.brown \
--to=neilb@suse.de \
--cc=drescherjm@gmail.com \
--cc=lilofile@aliyun.com \
--cc=linux-raid@vger.kernel.org \
--cc=stan@hardwarefreak.com \
/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).