* Drives re-added as spares instead of put back into array in rebuild mode
@ 2010-03-21 14:44 Randy Terbush
0 siblings, 0 replies; only message in thread
From: Randy Terbush @ 2010-03-21 14:44 UTC (permalink / raw)
To: linux raid
I had two drives that were dropped from this four drive array.
After going through failing, removing and re-adding the drives, I am
left with the following state. The two drives that were re-added are
sitting as spares and there is no rebuilding activity going on. Can
someone explain where I am going wrong?
mdadm --detail --scan /dev/md0
/dev/md0:
Version : 1.01
Creation Time : Wed Mar 17 15:27:33 2010
Raid Level : raid5
Array Size : 1465127424 (1397.25 GiB 1500.29 GB)
Used Dev Size : 488375808 (465.75 GiB 500.10 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Sun Mar 21 08:26:09 2010
State : active, degraded
Active Devices : 2
Working Devices : 4
Failed Devices : 0
Spare Devices : 2
Layout : left-symmetric
Chunk Size : 64K
Name : hifi:0 (local to host hifi)
UUID : b411b304:6385f171:26f07cb1:3c2b03de
Events : 1300
Number Major Minor RaidDevice State
0 8 17 0 active sync /dev/sdb1
1 0 0 1 removed
2 0 0 2 removed
4 8 65 3 active sync /dev/sde1
1 8 33 - spare /dev/sdc1
2 8 49 - spare /dev/sdd1
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-03-21 14:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-03-21 14:44 Drives re-added as spares instead of put back into array in rebuild mode Randy Terbush
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).