Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.