Ubuntu
mdadm package

[18.04.1] Backport support for Intel VROC arrays in mdadm

Bug #1779685 reported by Dimitri John Ledkov
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
Fix Released
High
Dimitri John Ledkov
Ubuntu ubuntu-18.04.1
Cosmic
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

 * mdadm as shipped in 18.04.0 does not support Intel VROC arrays, as to be shipped over Bionic LTS lifecycle in multiple laptop/desktop/server SKUs by multiple OEMs.

 * this is a request to backport mdadm master, with support of Intel VROC arrays, and subsequent compiler fixes, and reshaping fixes, to fully support VROC arrays (including reshaping).

[Test Cases]

 * Ensure existing Intel IMSM raids continue to assemble, boot, shutdown cleanly, bootable when degraded.
 * Ensure existing linux raids continue to assemble, boot, shutdown cleanly, bootable when degraded.
   - with 0.90 metadata; 1.0 metadata; 1.1 metadata; 1.2 metadata
 * [Optional] ensure that DDF raids continue to assemble, boot, shutdown cleanly, bootable when degraded.
 * Validate installers onto Intel IMSM raids
 * Validate installers onto Linux RAID
 * Validate bare-metal public clouds that use mdadm

[Regression Potential]

 * Worst case scenario is failing to start assembled array in rw mode, on boot. This would result in dropping into emergency shell/mode in either initramfs, or emergency.target requiring manual intervention by a sysadmin to recover and start synced raid array. However, the test cases above should cover this regression potential adequately.

 * Other changes, to resizing/reshaping may result in failure to resize/reshape, but these are rare maintenance operations for which one should have a backup - or able to recover from such an operation.

[Other Info]

 * xnox offline 7th July - 16th July

See original description
Dimitri John Ledkov (xnox)
Changed in mdadm (Ubuntu Cosmic):
status: New → Fix Released
Changed in mdadm (Ubuntu Bionic):
status: New → In Progress
importance: Undecided → High
milestone: none → ubuntu-18.04.1
assignee: nobody → Dimitri John Ledkov 🌈 (xnox)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote :

reviewing the diff, my biggest concern is that there appear to be new udev rules upstream. Are we going to be shipping these new upstream udev rules in the mdadm package? Have you examined the impact on other block layers, in particular lvm where I believe we are shipping non-upstream rules?

Changed in mdadm (Ubuntu Bionic):
status: In Progress → Incomplete
Revision history for this message
Dimitri John Ledkov (xnox) wrote : Re: [Bug 1779685] Re: [18.04.1] Backport support for Intel VROC arrays in mdadm

On Wed, 4 Jul 2018, 22:05 Steve Langasek, <email address hidden>
wrote:

> reviewing the diff, my biggest concern is that there appear to be new
> udev rules upstream. Are we going to be shipping these new upstream
> udev rules in the mdadm package? Have you examined the impact on other
> block layers, in particular lvm where I believe we are shipping non-
> upstream rules?
>

Yes there are new additional udev rules.

The safe timeout one, is auxiliary, and does not affect any other parts of
the system. Also, it looks like it would fail on non-usrmerged systems and
thus needs adjustment.

The creation udev rule, should not affect the state of the raid devices
during raid controller assembly. As this stamp file affects only initial
assembly/creation of raid devices. His is mostly for internal state
tracking / marking device systemd unit as ready.

Clustering support udev rules I cannot comment on. As I am yet to use
clustering support. And our installers do not set these up. Validating, and
correcting (if needed) clustering support is an open task for development
series.

>

Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Dimitri, 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.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-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!

Changed in mdadm (Ubuntu Bionic):
status: Incomplete → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Validated 1.2 metadata, installer/upgrades/booting/assembly/rebooting/degraded-boot all is good.
Validated known public cloud user of mdadm.
Validated upgrade/booting/assembly/rebooting of Intel matrix raid.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Cannot test IMSM installation, as new qemu/ovmf/something is preventing me to access intel matrix raid in the UEFI VM now. It used to work, however. Will investigate separately.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Validated 0.90 metadata.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Validated 1.0 metadata.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Validated 1.1 metadata.

tags: added: verification-done verification-done-bionic
removed: verification-needed verification-needed-bionic
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * No-change backport to bionic to enable Intel VROC support LP: #1779685

mdadm (4.1~rc1-3) unstable; urgency=medium

  * Cherrypick master patches up to 4th of June 2018.

mdadm (4.1~rc1-1) unstable; urgency=medium

  * New upstream release.
  * Import patches since rc1.
  * Bump standards version & debhelper compat.

 -- Dimitri John Ledkov 🌈 <email address hidden> Mon, 02 Jul 2018 14:26:00 +0100

Changed in mdadm (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

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.

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

I can not install the system by the daily bionic and cosmic desktop images on Intel VROC.
So I reported another issue, i.e. LP: #1792883.

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

LP: #1793444 is a following issue after this.

Revision history for this message
Yuriy (burtsevyg) wrote :

Can not install on Supermicro MBD X10DRi Ubuntu server 20.04. I see two disk. When I try to install on one of them I get error.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.