Mdadm: external metadata arrays and containers are removed incorrectly

Fixed in upstream:
https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=cb8f5371352f6c16af5aab8a40861e13aa50fc2b

Fix is included in mdadm 4.1, please update mdadm package.

Thanks,
Mariusz

Status changed to 'Confirmed' because the bug affects multiple users.

Hi,
Are there any update on this one?

Thanks
Pawel

The fix is in 4.1 which is released into Ubuntu 19.04 already
There are 4.1~rc1 based versions in 18.04 and 18.10 which do not contain the fix.

Which release are we talking about being affected - Bionic?

Yes, Bionic

Thanks, Mariusz

Hi,
It is fixed in 19.04 (mdadm there is 4.1).
Any chances to include the fix in 18.04 LTS?

Thanks
Pawel

Hi,
I need your help in testing this.
I have created a PPA [1] with the fixes for this issue, but I lack a IMSM HW.

I'd ask the people affected/subscribed to test the PPA.
While doing so please
a) ensure the test steps you have trigger the bug without the PPA
b) ensure the PPA fixes the issue
c) provide the exact steps (commands) that you used to test this (we want to add this to the SRU description)

[1]: https://launchpad.net/~paelzer/+archive/ubuntu/bug-1811228-1811795-mdadm-imsm

Incomplete waiting for PAP verification and better test steps

Hi,
Here test steps:
1. Create IMSM Container:
    mdadm -CR imsm0 -e imsm -n 2 /dev/sd[bc]
2. Create IMSM level 0 Array:
    mdadm -CR vol0 -l 0 -n 2 /dev/sd[bc]
3. Wait for resync to complete
   mdadm --wait /dev/md/vol0
4. Read /proc/mdstat and check /dev/md/ directory
   cat /proc/mdstat
   ls /dev/md/
5. Fail one disk incrementaly (simulate device disappearing from system)
   mdadm -If sdc
6. Check mdstat file and /dev/md/
   cat /proc/mdstat
   ls /dev/md/
Result:
   After disk fail [5] raid 0 array should disappear from mdstat, link /dev/md/imsm0 should exist.

The issue is fixed in PPA.

Thanks,
Mariusz

Thanks for the real test steps and checking them Mariusz.

This will now go to the review by the SRU Team.
Once accepted they will ask for a verification in -proposed (of both affected releases).
Once that is complete this can be released to all users.

Hello Mariusz, or anyone else affected,

Accepted mdadm into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mdadm/4.1~rc1-4ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Mariusz, or anyone else affected,

Accepted mdadm into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mdadm/4.1~rc1-3~ubuntu18.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hi,
the issue is fixed in bionic-proposed.

Thanks,
Mariusz

Thanks Mariusz!
Since this verification needs special HW which at least I currently have none of - do you see a chance to also do the verification for cosmic-proposed? Lacking that it can't be really released for Bionic as it would then become an upgrade-regression.

Hi,

I have tested issue in cosmic-proposed. It is fixed.

Regards,
Krzysztof

This bug was fixed in the package mdadm - 4.1~rc1-4ubuntu1.1

---------------
mdadm (4.1~rc1-4ubuntu1.1) cosmic; urgency=medium

  * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid
    creating whitespaced or empty names (LP: #1811228)
  * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of
    failing disks with external metadata (LP: #1811795)

 -- Christian Ehrhardt <email address hidden> Wed, 10 Apr 2019 16:14:17 +0200

This bug was fixed in the package mdadm - 4.1~rc1-3~ubuntu18.04.2

---------------
mdadm (4.1~rc1-3~ubuntu18.04.2) bionic; urgency=medium

  * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid
    creating whitespaced or empty names (LP: #1811228)
  * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of
    failing disks with external metadata (LP: #1811795)

 -- Christian Ehrhardt <email address hidden> Wed, 10 Apr 2019 16:14:17 +0200

The verification of the Stable Release Update for mdadm has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.