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

[Michał Żyłowski]

Private bug reported:


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 <mariusz.dabrowski at intel.com>
"imsm: add functions to get and set imsm dev size" fcc2c9daede11fcc67e4032fd6fa8da198aaa319 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
"imsm: pass already existing map to imsm_num_data_members" 9529d3436771d9f38884861683dee3b40ab9d180 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
"imsm: do not use blocks_per_member in array size calculations" 444909385fdaccf961308c4319d7029b82bf8bb1 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
"imsm: correct num_data_stripes in metadata map for migration" 4a353e6ec48e35437b27978add6cd2cd015f2cfe by Roman Sobanski <roman.sobanski at intel.com>

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

** Affects: mdadm (Ubuntu)
     Importance: Undecided
         Status: New

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mdadm in Ubuntu.
https://bugs.launchpad.net/bugs/1781427

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

Status in mdadm package in Ubuntu:
  New

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 <mariusz.dabrowski at intel.com>
  "imsm: add functions to get and set imsm dev size" fcc2c9daede11fcc67e4032fd6fa8da198aaa319 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
  "imsm: pass already existing map to imsm_num_data_members" 9529d3436771d9f38884861683dee3b40ab9d180 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
  "imsm: do not use blocks_per_member in array size calculations" 444909385fdaccf961308c4319d7029b82bf8bb1 by Mariusz Dabrowski <mariusz.dabrowski at intel.com>
  "imsm: correct num_data_stripes in metadata map for migration" 4a353e6ec48e35437b27978add6cd2cd015f2cfe by Roman Sobanski <roman.sobanski at intel.com>

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1781427/+subscriptions