[INTEL UBUNTU 18.04/18.10 BUG] Wrong size after OLCE of IMSM Volume
| 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" 611d95290dd41d7
"imsm: add functions to get and set imsm dev size" fcc2c9daede11fc
"imsm: pass already existing map to imsm_num_
"imsm: do not use blocks_per_member in array size calculations" 444909385fdaccf
"imsm: correct num_data_stripes in metadata map for migration" 4a353e6ec48e354
All patches are accepted in upstream and pushed: https:/
| information type: | Public → Private |
| Dimitri John Ledkov (xnox) wrote | #1 |
| Dimitri John Ledkov (xnox) wrote | #2 |
| information type: | Private → Public |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in mdadm (Ubuntu Cosmic): | |
| status: | New → Fix Released |
This bug needs to be public, for me to reference in the changelogs for auto-closing and the SRU process.