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:

I wanted to try out mdadm Software Raid 1 and assigned two FC LUNs to a test Server and did a standard Setup. After successfull setup i deassigned one of the two LUNs to simulate a desaster szenario. The software raid became unusable.


Version-Release number of selected component (if applicable):

mdadm-3.2.5-4.el6_4.1.i686

How reproducible:


Steps to Reproduce:
1. Assign two fc luns fc-lun1 fc-lun2 
2. create software raid 1: mdadm --create  --verbose /dev/md0 --level=mirror --raid-devices=2 /dev/mapper/fc-lun1 /dev/mapper/fc-lun2 
3. mkfs.ext4  /dev/md0 + mount /dev/md0 /mnt/test
4. deassign one of the luns from step1

Actual results:

- mdadm --detail /dev/md0 ---> does not terminate
- cat /proc/mdstat ---> does not terminate
- /mnt/test is not writable

Expected results:

- raid status info with the commands
mdadm --detail /dev/md0 or
cat /proc/mdstat
- writeble /mnt/test filesystem


Additional info:
words cannot describe my disappointment

i will recheck my multipath setup, maybe multipath tries to hide the path loss ....

OK, sorry guys this was my fault (wrong multipath.conf), very embarrassing. Ticket can be closed.

OK, closing out.  Glad to hear it works for you ;-)