[INTEL UBUNTU 18.04/18.10 BUG] Wrong size after OLCE of IMSM Volume

Bug #1781427 reported by Michał Żyłowski
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mdadm (Ubuntu)
Fix Released
Undecided
Unassigned
Bionic
New
Undecided
Unassigned
Cosmic
Fix Released
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. Create RAID volume using PreOS environment.
2. Boot to OS.
3. Add additional drive(s) to an IMSM array using command: mdadm --add /dev/imsm0 /dev/sd[a-z] drives with capacity greater or equal smallest drive capacity used in IMSM array
4. Execute grow command on array with additional drives: mdadm --grow /dev/md/imsm0 --raid-devices=N Where N is number of drives after resizing
5. Check if volume on IMSM array was proportionally resized.

Expected results:
Raid volume after OLCE should have proper size.

Actual results:
Raid volume size didn’t change after OLCE.

This bug is fixed in upstream by few patches. They have to be applied to ubuntu mdadm package.

List of necessary patches:
"imsm: change reserved space to 4MB" 611d95290dd41d73bd8f9cc06f7ec293a40b819e by Mariusz Dabrowski <email address hidden>
"imsm: add functions to get and set imsm dev size" fcc2c9daede11fcc67e4032fd6fa8da198aaa319 by Mariusz Dabrowski <email address hidden>
"imsm: pass already existing map to imsm_num_data_members" 9529d3436771d9f38884861683dee3b40ab9d180 by Mariusz Dabrowski <email address hidden>
"imsm: do not use blocks_per_member in array size calculations" 444909385fdaccf961308c4319d7029b82bf8bb1 by Mariusz Dabrowski <email address hidden>
"imsm: correct num_data_stripes in metadata map for migration" 4a353e6ec48e35437b27978add6cd2cd015f2cfe by Roman Sobanski <email address hidden>

All patches are accepted in upstream and pushed: https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/log/

information type: Public → Private
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

This bug needs to be public, for me to reference in the changelogs for auto-closing and the SRU process.

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

I see no private information posted to this bug, therefore making it public.

information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

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

  * Cherrypick master patches up to 20th of July 2018. LP: #1781427
  * Make safe-timouts udev rules compatible with usr-split systems.

 -- Dimitri John Ledkov <email address hidden> Mon, 23 Jul 2018 11:48:50 +0100

Changed in mdadm (Ubuntu Cosmic):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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