From: Alberto Alonso <alberto@ggsys.net>
To: linux-raid@vger.kernel.org
Subject: Kicking the right drive out
Date: Sat, 13 Oct 2007 13:00:16 -0500 [thread overview]
Message-ID: <1192298416.16416.246.camel@w100> (raw)
I have a need to kick a disk out of a RAID 5 array.
I can do a fdisk on 2 out of the 3 devices that form part
of the array, so I suspect I know which one is bad.
The problem is that mdstat shows the array as follows:
md3 : active raid5 sda6[0] sdc6[2] sdb6[1]
960863488 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
[>....................] resync = 0.7% (3444348/480431744)
finish=582280.4min speed=1K/sec
Doesn't this mean that all three disks are active and in use?
mdadm -D /dev/md3 shows:
Number Major Minor RaidDevice State
0 8 6 0 active sync /dev/sda6
1 8 22 1 active sync /dev/sdb6
2 8 38 2 active sync /dev/sdc6
So, my question is as follows: can I remove sdc6 and be sure the
array will not stop?
To make things worse, I see no disk failures in any log file. So
I am not sure how sdc is actually failing.
Thanks,
Alberto
next reply other threads:[~2007-10-13 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 18:00 Alberto Alonso [this message]
2007-10-14 8:49 ` Kicking the right drive out Nagilum
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=1192298416.16416.246.camel@w100 \
--to=alberto@ggsys.net \
--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).