Hide Forgot
Description of problem: After removing a disk from a raid1 array I cannot re-add that disk to the array Version-Release number of selected component (if applicable): kernel-2.6.32-220.4.1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1.mdadm /dev/md3 -f /dev/sdc1 2.mdadm /dev/md3 -r /dev/sdc1 3.mdadm /dev/md3 -a /dev/sdc1 Actual results: [root@ferguson ~]# mdadm /dev/md3 -a /dev/sdc1 mdadm: /dev/sdc1 reports being an active member for /dev/md3, but a --re-add fails. mdadm: not performing --add as that would convert /dev/sdc1 in to a spare. mdadm: To make this a spare, use "mdadm --zero-superblock /dev/sdc1" first. [root@ferguson ~]# Expected results: disk is added back into the raid1 array. Additional info: I have tried using a new version of dracut and dracut-kernel dracut-004-256.el6_2.1.noarch dracut-kernel-004-256.el6_2.1.noarch rebuilding initramfs with mkinitrd --force /boot/initramfs-2.6.32-220.4.1.el6.x86_64.img 2.6.32-220.4.1.el6.x86_64 but it still fails. If I reboot with kernel-2.6.32-131.21.1.el6.x86_64 I am able to re-add the disk.
I tried the new kernel-2.6.32-220.4.2.el6.x86_64 that Scientific Linux just released, but it still has the same issue. BTW Perhaps I should have mentioned I'm running SL 6.2 upgraded from SL 6.1
1) If you try to re-add a disk to a running raid1 after having failed it, mdadm correctly rejects it as it has no way of knowing which of the disks are authoritative. It clearly tells you that in the error message you pasted into the bug. 2) You reported a Scientific Linux bug against Red Hat Enterprise Linux. Red Hat does not support Scientific Linux, please report bugs against Scientific Linux to the people behind Scientific Linux.
What a load of bullshit. Think again!
My apologies for my previous comment. Please ignore it.