Francois Barre wrote:
> Well, Neil, I'm wondering,
> It seemed to me that Akos' description of the problem was that
> re-adding the drive (with mdadm not complaining about anything) would
> trigger a resync that would not even start.
> But as your '--force' does the trick, it implies that the resync was
> not really triggered after all without it... Or did I miss a bit of
> log Akos provided that did say so ?
> Could there be a place here for an error message ?
well, thing is it's still not totally OK. after doing an
# mdadm -A --force /dev/md0
# mdadm /dev/md0 -a /dev/sdb1
it starts to re-assemble the array. it takes a lot of time (like about 4
hours), which is OK. after the re-assembly is ready, all seems fine:
# cat /proc/mdstat
Personalities : [raid5] [raid4]
md0 : active raid5 sdb1[1] sda1[0] sdd1[3] sdc1[2]
1172126208 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
unused devices: <none>
# mdadm --query /dev/md0
/dev/md0: 1117.83GiB raid5 4 devices, 0 spares. Use mdadm --detail for
more detail.
# mdadm --query --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Tue Apr 25 16:17:14 2006
Raid Level : raid5
Array Size : 1172126208 (1117.83 GiB 1200.26 GB)
Device Size : 390708736 (372.61 GiB 400.09 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Mon Jul 3 00:16:39 2006
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 8a66d568:0be5b0a0:93b729eb:6f23c014
Events : 0.2701837
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
2 8 33 2 active sync /dev/sdc1
3 8 49 3 active sync /dev/sdd1
#
right? checking with
# mdadm -E /dev/sb[a-d]1
will also show that all drives have the same event count, etc.
but, just doing a
# mdadm --stop /dev/md0
# mdadm -A /dev/md0
will result in the array started with 3 drives out of 4 again. what am I
doing wrong?
Akos
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
