Description of problem: First stop command (mdadm -Ss) cannot stop container during volume's reshape. Stopping for the second time works. How reproducible: Always Steps to Reproduce: 1. Create container and volume: # mdadm -CR /dev/md/imsm -e imsm -n3 /dev/sda /dev/sdc /dev/sdd # mdadm -CR /dev/md/vol -l0 -n2 /dev/sda /dev/sdc 2. Run OLCE: # export MDADM_EXPERIMENTAL=1 # mdadm -G /dev/md127 -n3 3. Stop all RAID devices # mdadm -Ss Actual results: Volume is stopped, but container not. Output: # mdadm -Ss mdadm: stopped /dev/md126 mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group? mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process, mounted filesystem or active volume group? After next stop command container is stopped correctly: mdadm -Ss mdadm: stopped /dev/md126 mdadm: stopped /dev/md127 Expected results: Volume and container are stopped: mdadm: stopped /dev/md126 mdadm: stopped /dev/md127 Additional info: This bug is fixed by the following upstream patch: commit 2fdf559d74a48806900b63f1b4504a18dec048a9 Manage_runstop: call flush_mdmon if O_EXCL fails on stopping mdmon array. http://git.neil.brown.name/git?p=mdadm.git;a=commit;h=2fdf559d74a48806900b63f1b4504a18dec048a9
mdadm-3.2.6-21.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/mdadm-3.2.6-21.fc19
Package mdadm-3.2.6-21.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mdadm-3.2.6-21.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-14685/mdadm-3.2.6-21.fc19 then log in and leave karma (feedback).
mdadm-3.2.6-21.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.