From: "J. David Beutel" <jdb@getsu.com>
To: linux-raid@vger.kernel.org
Subject: reducing the number of disks a RAID1 expects
Date: Sun, 09 Sep 2007 15:10:41 -1000 [thread overview]
Message-ID: <46E49991.9000000@getsu.com> (raw)
My /dev/hdd started failing its SMART check, so I removed it from a RAID1:
# mdadm /dev/md5 -f /dev/hdd2 -r /dev/hdd2
Now when I boot it looks like this in /proc/mdstat:
md5 : active raid1 hdc8[2] hdg8[1]
58604992 blocks [3/2] [_UU]
and I get a "DegradedArray event on /dev/md5" email on every boot from
mdadm monitoring. I only need 2 disks in md5 now. How can I stop it
from being considered "degraded"? I added a 3rd disk a while ago just
because I got a new disk with plenty of space, and little /dev/hdd was
getting old.
mdadm - v1.6.0 - 4 June 2004
Linux 2.6.12-1.1381_FC3 #1 Fri Oct 21 03:46:55 EDT 2005 i686 athlon i386
GNU/Linux
Cheers,
11011011
next reply other threads:[~2007-09-10 1:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 1:10 J. David Beutel [this message]
2007-09-10 2:29 ` reducing the number of disks a RAID1 expects Richard Scobie
2007-09-10 7:31 ` J. David Beutel
2007-09-10 9:55 ` Iustin Pop
2007-09-11 13:33 ` Bill Davidsen
2007-09-11 14:04 ` Neil Brown
2007-09-15 21:13 ` J. David Beutel
2007-09-16 22:09 ` Goswin von Brederlow
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=46E49991.9000000@getsu.com \
--to=jdb@getsu.com \
--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).