[Bug 2070371] Re: [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch

[Launchpad Bug Tracker]

This bug was fixed in the package mdadm - 4.3-1ubuntu2.1

---------------
mdadm (4.3-1ubuntu2.1) noble; urgency=medium

  * mdadm: wait for mdmon when it is started via systemd (LP: #2070371)
    - d/p/lp2070371-0001-util.c-change-devnm-to-const-in-mdmon-functions.patch
    - d/p/lp2070371-0002-Wait-for-mdmon-when-it-is-stared-via-systemd.patch
  * mdadm: buffer overflow detected (LP: #2069821)
    - d/p/lp2069821-0001-mdadm-platform-intel-buffer-overflow-detected.patch

 -- Hector Cao <hector.cao at canonical.com>  Mon, 29 Jul 2024 10:06:31
+0200

** Changed in: mdadm (Ubuntu Noble)
       Status: Fix Committed => Fix Released

-- 
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/2070371

Title:
  [VROC] [Ub 24.04] mdadm: grow for R0 not start - missing patch

Status in mdadm package in Ubuntu:
  Fix Released
Status in mdadm source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  This bug prevents users from successfully reshaping/growing a RAID array
  Indeed, at the reshaping operation, for external array, mdadm might miss
  the mdmon daemon up and running event because mdadm only runs and check
  if it is running without waiting.

  This fix introduces a timed_wait operation that allows mdadm to wait
  for 5 seconds the mdmon running event and minimizes the risk of
  missing it.

  [ Test Plan ]

  
  Steps to reproduce:
  1. Create RAID volume e.g.:
  # mdadm -C /dev/md/imsm0 -e imsm -n 2 /dev/nvme0n1 /dev/nvme1n1 -R
  # mdadm -C /dev/md/MyVolume -l0 -n 2 /dev/nvme[0-1]n1 -R
  2. Add additional drive(s) to an IMSM array using command e.g.:
  # mdadm --add /dev/md/imsm0 /dev/nvme2n1
  3. Execute grow command on array with additional drives:
  # mdadm --grow /dev/md/imsm0 --raid-devices=N
  4. Wait for reshape start on given volume
  # cat /proc/mdstat

  Expected result:

  Reshape started successfully, no errors reported

  Actual result:

  Reshape didn't start on given volume

  
  [ Where problems could occur ]

  The change only affects the Grow/Reshape operation of mdadm
  and i do not expect problems to occur in other places. 

  [ Other Info ]

  This fix has been already merged upstreamed:

  -
  https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=b0f4e8e30f38d83f7e3f53d01d72d4cb3b4d42d7

  -
  https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/commit/?id=aa1cc5815d2b14a8b47add18cfaa8264e19c10ce

  The fix is in the second commit, the first commit is a dependency of
  the second commit and it is only about a minor change in a function
  signature.

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