Change log for mdadm package in Ubuntu

mdadm (4.2+20230508-7ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable. Remaining changes:
    - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd:
      Ship finalrd hook
    - d/local/initramfs-tools/init-top/00_mount_efivarfs:
      Mount efivarfs during initramfs boot phase
    - d/mdadm.maintscript: Keep Ubuntu prior-versions until after
      the release of 24.04

Available diffs

• diff from 4.2+20230508-6ubuntu1 to 4.2+20230508-7ubuntu1 (916 bytes)

mdadm (4.2+20230508-6ubuntu1) mantic; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - d/control, d/mdadm.install, d/local/finalrd/mdadm.finalrd:
      Ship finalrd hook
    - d/local/initramfs-tools/init-top/00_mount_efivarfs:
      Mount efivarfs during initramfs boot phase
  * d/mdadm.maintscript: Keep Ubuntu prior-versions until after
    the release of 24.04
  * Dropped changes, included in Debian:
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm

Available diffs

• diff from 4.2-5ubuntu2 to 4.2+20230508-6ubuntu1 (163.4 KiB)

mdadm (4.2-0ubuntu2) jammy; urgency=medium

  * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541)

 -- Cyrus Lien <email address hidden>  Tue, 11 Apr 2023 11:22:59 +0800

Available diffs

• diff from 4.2-0ubuntu1 to 4.2-0ubuntu2 (747 bytes)

mdadm (4.2-3ubuntu2) kinetic; urgency=medium

  * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541)

 -- Cyrus Lien <email address hidden>  Tue, 11 Apr 2023 11:22:59 +0800

Available diffs

• diff from 4.2-3ubuntu1 to 4.2-3ubuntu2 (584 bytes)

mdadm (4.2-5ubuntu2) lunar; urgency=medium

  * Add scripts/init-top/00_mount_efivarfs, mounting efivarfs. (LP: #1993541)

 -- Cyrus Lien <email address hidden>  Tue, 11 Apr 2023 11:22:59 +0800

Available diffs

• diff from 4.2-5ubuntu1 to 4.2-5ubuntu2 (571 bytes)

mdadm (4.2-5ubuntu1) lunar; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm
  * Dropped changes, included in Debian:
    - Install /usr/share/apport/package-hooks/source_mdadm.py with install
      instead of a second call to dh_install, which clears the execute
      permission on /usr/share/mdadm/mdcheck
    - Drop /lib/udev/rules.d/64-md-raid-assembly.rules from mdadm-udeb,
      no longer built
    - Ship /etc/mdadm directory again to prevent dpkg warning:
      unable to delete old directory '/etc/mdadm': Directory not empty
    - Display $(DEB_VENDOR) $(DEB_VERSION) in mdadm --version output

Available diffs

• diff from 4.2-3ubuntu1 to 4.2-5ubuntu1 (2.6 KiB)

mdadm (4.2-3ubuntu1) kinetic; urgency=medium

  * Merge from Debian unstable, remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm
  * Install /usr/share/apport/package-hooks/source_mdadm.py with install
    instead of a second call to dh_install, which clears the execute
    permission on /usr/share/mdadm/mdcheck
  * Drop /lib/udev/rules.d/64-md-raid-assembly.rules from mdadm-udeb,
    no longer built
  * Ship /etc/mdadm directory again to prevent dpkg warning:
    unable to delete old directory '/etc/mdadm': Directory not empty,
    see #1004475
  * Display $(DEB_VENDOR) $(DEB_VERSION) in mdadm --version output,
    see #1000663

Available diffs

• diff from 4.2-0ubuntu1 to 4.2-3ubuntu1 (14.7 KiB)

mdadm (4.2-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1959843)

 -- Graham Inggs <email address hidden>  Thu, 24 Feb 2022 15:19:00 +0000

Available diffs

• diff from 4.2~rc2-2ubuntu1 to 4.2-0ubuntu1 (12.0 KiB)

mdadm (4.2~rc2-2ubuntu1) impish; urgency=medium

  * Merge from Debian unstable (LP: #1940096), remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm

Available diffs

• diff from 4.2~rc1-1ubuntu1 to 4.2~rc2-2ubuntu1 (17.5 KiB)

mdadm (4.2~rc1-1ubuntu1) impish; urgency=medium

  * Merge from Debian experimental (LP: #1935895), remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
      in /etc/default/mdadm
  * Dropped changes:
    - d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
      - When mdcheck_start is enabled, enable mdcheck_continue too.
    - d/p/mdcheck-log-when-done.patch:
      - Make sure mdcheck logs the completion too, so that
      it can be determined how long the raid check took.
    - Cherrypick upstream fix to allow assembling dirty degrated IMSM raid
      arrays with --force flag

Available diffs

• diff from 4.1-11ubuntu1 to 4.2~rc1-1ubuntu1 (90.6 KiB)

mdadm (4.1-11ubuntu1) impish; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
      - When mdcheck_start is enabled, enable mdcheck_continue too.
    - d/p/mdcheck-log-when-done.patch:
      - Make sure mdcheck logs the completion too, so that
      it can be determined how long the raid check took.
    - Cherrypick upstream fix to allow assembling dirty degrated IMSM raid
      arrays with --force flag
  * Mention mdmonitor-oneshot.service instead of /etc/cron.daily/mdadm
    in /etc/default/mdadm

Available diffs

• diff from 4.1-10ubuntu3 to 4.1-11ubuntu1 (1.9 KiB)

mdadm (4.1-10ubuntu3) hirsute; urgency=medium

  * No-change rebuild to drop the udeb package.

 -- Matthias Klose <email address hidden>  Thu, 25 Feb 2021 06:59:03 +0100

Available diffs

• diff from 4.1-10ubuntu2 to 4.1-10ubuntu3 (292 bytes)

mdadm (4.1-10ubuntu2) hirsute; urgency=medium

  * No-change rebuild to drop the udeb package.

 -- Matthias Klose <email address hidden>  Mon, 22 Feb 2021 10:35:27 +0100

Available diffs

• diff from 4.1-10ubuntu1 to 4.1-10ubuntu2 (322 bytes)

mdadm (4.1-10ubuntu1) hirsute; urgency=medium

  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
      - When mdcheck_start is enabled, enable mdcheck_continue too.
    - d/p/mdcheck-log-when-done.patch:
      - Make sure mdcheck logs the completion too, so that
      it can be determined how long the raid check took.
    - Cherrypick upstream fix to allow assembling dirty degrated IMSM raid
      arrays with --force flag

Available diffs

• diff from 4.1-8ubuntu1 to 4.1-10ubuntu1 (3.5 KiB)

mdadm (4.1-8ubuntu1) hirsute; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.
    - d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
      - The spaces were causing a FTBFS situation, triggered by
        dh_installsystemd not finding units.
    - d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
      - When mdcheck_start is enabled, enable mdcheck_continue too.
    - d/p/mdcheck-log-when-done.patch:
      - Make sure mdcheck logs the completion too, so that
      it can be determined how long the raid check took.

  * Also fix up whitespace in systemd/mdmonitor-oneshot.timer.
  * Cherrypick upstream fix to allow assembling dirty degrated IMSM raid
    arrays with --force flag. LP: #1894792

Available diffs

• diff from 4.1-5ubuntu5 to 4.1-8ubuntu1 (38.0 KiB)

mdadm (4.1-5ubuntu1.2) focal; urgency=medium

  * d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
    - When mdcheck_start is enabled, enable mdcheck_continue too.

Available diffs

• diff from 4.1-5ubuntu1.1 to 4.1-5ubuntu1.2 (989 bytes)

mdadm (4.1-5ubuntu5) groovy; urgency=medium

  * d/p/mdcheck-fix-empty-spaces-in-timer-unit-files.patch:
    - The spaces were causing a FTBFS situation, triggered by
      dh_installsystemd not finding units.

Available diffs

• diff from 4.1-5ubuntu3 to 4.1-5ubuntu5 (1.2 KiB)
• diff from 4.1-5ubuntu4 to 4.1-5ubuntu5 (774 bytes)

mdadm (4.1-5ubuntu4) groovy; urgency=medium

  * d/p/mdcheck-when-mdcheck-start-is-enabled-mdcheck-continue-too.patch:
    - When mdcheck_start is enabled, enable mdcheck_continue too.

Available diffs

• diff from 4.1-5ubuntu3 to 4.1-5ubuntu4 (962 bytes)

mdadm (4.1-5ubuntu3) groovy; urgency=medium

  * d/p/mdcheck-log-when-done.patch:
    - Make sure mdcheck logs the completion too, so that
     it can be determined how long the raid check took.

 -- Eric Desrochers <email address hidden>  Thu, 24 Sep 2020 09:14:49 -0400

Available diffs

• diff from 4.1-5ubuntu2 to 4.1-5ubuntu3 (1.0 KiB)

mdadm (4.1-5ubuntu1.1) focal; urgency=medium

  * d/rules: Install misc/mdcheck (LP: #1852747)
    - The absence of mdcheck utility is preventing
      mdcheck_continue.service & mdcheck_start.service
      to execute the command when the service start via
      ExecStart. (Closes: #960132)

  * d/p/mdcheck-log-when-done.patch:
    - Make sure mdcheck logs the completion too, so that
      it can be determined how long the raid check took.

 -- Eric Desrochers <email address hidden>  Thu, 24 Sep 2020 07:54:15 -0400

Available diffs

• diff from 4.1-5ubuntu1 to 4.1-5ubuntu1.1 (1.3 KiB)

mdadm (4.1-5ubuntu2) groovy; urgency=medium

  * d/rules: Install misc/mdcheck (LP: #1852747)
    - The absence of mdcheck utility is preventing
      mdcheck_continue.service & mdcheck_start.service
      to execute the command when the service start via
      ExecStart. (Closes: #960132)

 -- Eric Desrochers <email address hidden>  Wed, 23 Sep 2020 14:08:32 -0400

Available diffs

• diff from 4.1-5ubuntu1 to 4.1-5ubuntu2 (609 bytes)

mdadm (4.1-5ubuntu1) focal; urgency=medium

  [ dann frazier ]
  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
    - Honor the debconf daily autoscan setting in the systemd timer.

Available diffs

• diff from 4.1-4ubuntu1 to 4.1-5ubuntu1 (3.2 KiB)

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

  * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
    - d/p/lp1847924-Introduce-new-array-state-broken-for-raid0.patch

  * Disable patches from proposed version 4.1~rc1-3~ubuntu18.04.3 due to
    issues with kernel

 -- <email address hidden> (Guilherme G. Piccoli)  Tue, 14 Jan 2020 16:10:59 -0300

Available diffs

• diff from 4.1~rc1-3~ubuntu18.04.2 to 4.1~rc1-3~ubuntu18.04.4 (8.6 KiB)
• diff from 4.1~rc1-3~ubuntu18.04.3 to 4.1~rc1-3~ubuntu18.04.4 (3.0 KiB)

mdadm (4.1-2ubuntu3.2) eoan; urgency=medium

  * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)
    - d/p/lp1847924-Introduce-new-array-state-broken-for-raid0.patch

  * Disable patches from proposed version 4.1-2ubuntu3.1 due to issues
    with kernel

 -- <email address hidden> (Guilherme G. Piccoli)  Tue, 14 Jan 2020 17:09:06 -0300

Available diffs

• diff from 4.1-2ubuntu3.1 to 4.1-2ubuntu3.2 (2.9 KiB)

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

  * Add support for RAID0 layouts. Released kernels are being updated
    to require an explicit layout version for multi-zone RAID0 arrays
    to avoid potential corruption. This update allows users to program
    such a layout version into the metadata of an array. LP: #1850540

 -- dann frazier <email address hidden>  Wed, 04 Dec 2019 12:52:00 -0700

Available diffs

• diff from 4.1~rc1-3~ubuntu18.04.2 to 4.1~rc1-3~ubuntu18.04.3 (6.5 KiB)

mdadm (4.1-1ubuntu1.1) disco; urgency=medium

  * Add support for RAID0 layouts. Released kernels are being updated
    to require an explicit layout version for multi-zone RAID0 arrays
    to avoid potential corruption. This update allows users to program
    such a layout version into the metadata of an array. LP: #1850540

 -- dann frazier <email address hidden>  Wed, 04 Dec 2019 12:44:30 -0700

Available diffs

• diff from 4.1-1ubuntu1 to 4.1-1ubuntu1.1 (6.4 KiB)

mdadm (4.1-2ubuntu3.1) eoan; urgency=medium

  * Add support for RAID0 layouts. Released kernels are being updated
    to require an explicit layout version for multi-zone RAID0 arrays
    to avoid potential corruption. This update allows users to program
    such a layout version into the metadata of an array. LP: #1850540

 -- dann frazier <email address hidden>  Wed, 04 Dec 2019 12:31:35 -0700

Available diffs

• diff from 4.1-2ubuntu3 to 4.1-2ubuntu3.1 (6.4 KiB)

mdadm (4.1-4ubuntu1) focal; urgency=medium

  [ dann frazier ]
  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.
    - Drop broken and unused init scripts in favor of native systemd units,
      which can cause failure to reconfigure mdadm package under certain
      confiment types.
    - Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
      timer units.
    - Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
      timer unit.
    - mdcheck_start.timer configures the mdcheck on a first sunday of the
      month, with a randomized start delay of up to 24h, and runs for at
      most 6h. mdcheck_continue.timer kicks off daily, with a randomized
      start delay of up to 12h, and continues mdcheck for at most 6h.
    - mdmonitor-oneshot.timer runs daily, with a randomized start delay of
      up to 24h.
    - One can use systemd drop-ins to change .timer units timings, set
      environmental variables to decrease/increase the length of checking,
      or start the checks by hand. Previously used checkarray is still
      available, albeit not used by timer units.
    - Above ensures that previous daily / monthly checks are performed, but
      are randomized, such that performance is not as impacted across a
      cluster of machines.
  * Honor the debconf daily autoscan setting in the systemd timer.

  [ Guilherme G. Piccoli ]
  * Introduce "broken" state for RAID0/Linear in mdadm (LP: #1847924)

 -- dann frazier <email address hidden>  Wed, 04 Dec 2019 07:05:07 -0700

Available diffs

• diff from 4.1-2ubuntu3 to 4.1-4ubuntu1 (13.8 KiB)

mdadm (4.1-2ubuntu3) eoan; urgency=medium

  * Drop /etc/cron.d/mdadm and migrate to systemd mdcheck_start|continue
    timer units.
  * Drop /etc/cron.daily/mdadm and migrate to system mdmonitor-oneshot
    timer unit.
  * mdcheck_start.timer configures the mdcheck on a first sunday of the
    month, with a randomized start delay of up to 24h, and runs for at
    most 6h. mdcheck_continue.timer kicks off daily, with a randomized
    start delay of up to 12h, and continues mdcheck for at most 6h.
  * mdmonitor-oneshot.timer runs daily, with a randomized start delay of
    up to 24h.
  * One can use systemd drop-ins to change .timer units timings, set
    environmental variables to decrease/increase the length of checking,
    or start the checks by hand. Previously used checkarray is still
    available, albeit not used by timer units.
  * Above ensures that previous daily / monthly checks are performed, but
    are randomized, such that performance is not as impacted across a
    cluster of machines. LP: #1815201

 -- Dimitri John Ledkov <email address hidden>  Tue, 18 Jun 2019 16:29:44 +0100

Available diffs

• diff from 4.1-2ubuntu2 to 4.1-2ubuntu3 (2.3 KiB)

mdadm (4.1-2ubuntu2) eoan; urgency=medium

  * Drop broken and unused init scripts in favor of native systemd units,
    which can cause failure to reconfigure mdadm package under certain
    confiment types. LP: #1829325

 -- Dimitri John Ledkov <email address hidden>  Mon, 20 May 2019 19:57:41 +0100

Available diffs

• diff from 4.1-2ubuntu1 to 4.1-2ubuntu2 (1.8 KiB)

mdadm (4.1-2ubuntu1) eoan; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.

Available diffs

• diff from 4.1-1ubuntu1 to 4.1-2ubuntu1 (757 bytes)

mdadm (4.1~rc1-4ubuntu1.1) cosmic; urgency=medium

  * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid
    creating whitespaced or empty names (LP: #1811228)
  * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of
    failing disks with external metadata (LP: #1811795)

 -- Christian Ehrhardt <email address hidden>  Wed, 10 Apr 2019 16:14:17 +0200

Available diffs

• diff from 4.1~rc1-4ubuntu1 to 4.1~rc1-4ubuntu1.1 (2.8 KiB)

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

  * d/p/lp-1811228-imsm-Block-volume-creation-with-empty-name.patch: avoid
    creating whitespaced or empty names (LP: #1811228)
  * d/p/lp-1811795-remove-external-arrays-and-devices.patch: fix removal of
    failing disks with external metadata (LP: #1811795)

 -- Christian Ehrhardt <email address hidden>  Wed, 10 Apr 2019 16:14:17 +0200

Available diffs

• diff from 4.1~rc1-3~ubuntu18.04.1 to 4.1~rc1-3~ubuntu18.04.2 (2.8 KiB)

mdadm (4.1-1ubuntu1) disco; urgency=low

  * Merge from Debian unstable.  Remaining changes:
    - Ship finalrd hook.
    - Do not install mdadm-shutdown.service on Ubuntu.

Available diffs

• diff from 4.1~rc1-4ubuntu1 to 4.1-1ubuntu1 (55.6 KiB)

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

  * Ship finalrd hook.
  * Do not install mdadm-shutdown.service on Ubuntu.

 -- Dimitri John Ledkov <email address hidden>  Fri, 03 Aug 2018 14:53:18 +0100

Available diffs

• diff from 4.1~rc1-4 (in Debian) to 4.1~rc1-4ubuntu1 (1.4 KiB)

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

Available diffs

• diff from 4.1~rc1-3 to 4.1~rc1-4 (14.3 KiB)

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

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

Available diffs

• diff from 4.0-2ubuntu1.1 to 4.1~rc1-3~ubuntu18.04.1 (148.0 KiB)

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

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

 -- Dimitri John Ledkov 🌈 <email address hidden>  Tue, 26 Jun 2018 15:38:04 +0100

Available diffs

• diff from 4.1~rc1-2 to 4.1~rc1-3 (12.4 KiB)

mdadm (4.0-2ubuntu1.1) bionic; urgency=medium

  * Install identical udev rules into d-i installer udeb, as used in the
    installed system. Specifically, post-processed rules with full path to
    mdadm binary subsituted, instead of installing useless rules with the
    template variable BINDIR. LP: #1705215

 -- Dimitri John Ledkov <email address hidden>  Thu, 24 May 2018 11:14:57 +0100

Available diffs

• diff from 4.0-2ubuntu1 to 4.0-2ubuntu1.1 (750 bytes)

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

  * Install identical udev rules into d-i installer udeb, as used in the
    installed system. Specifically, post-processed rules with full path to
    mdadm binary subsituted, instead of installing useless rules with the
    template variable BINDIR. LP: #1705215

 -- Dimitri John Ledkov <email address hidden>  Tue, 22 May 2018 14:26:59 +0100

Available diffs

• diff from 4.1~rc1-1 to 4.1~rc1-2 (722 bytes)

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>  Tue, 15 May 2018 12:10:33 +0100

Available diffs

• diff from 4.0-2ubuntu1 (in Ubuntu) to 4.1~rc1-1 (138.7 KiB)

mdadm (4.0-2ubuntu1) bionic; urgency=medium

  * Cherry-pick upstream patch to ensure mdadm-last-resort services
    only runs when it is needed LP: #1753786
    - debian/patches/mdadm-last-resort-use-condition-path-exists.patch

 -- Ryan Harper <email address hidden>  Wed, 07 Mar 2018 01:43:16 -0600

Available diffs

• diff from 4.0-2 (in Debian) to 4.0-2ubuntu1 (1.7 KiB)

mdadm (3.3-2ubuntu7.6) xenial; urgency=medium

  * Prevent segfault when get_md_name() returns NULL
    This fixes mdadm segfaults when running inside a container.
    (LP: #1617919)

 -- Dan Streetman <email address hidden>  Mon, 09 Oct 2017 10:06:22 -0400

Available diffs

• diff from 3.3-2ubuntu7.5 to 3.3-2ubuntu7.6 (1.2 KiB)

mdadm (3.2.5-5ubuntu4.4) trusty; urgency=medium

  * Prevent segfault when get_md_name() returns NULL
    This fixes mdadm segfaults when running inside a container.
    (LP: #1617919)

 -- Dan Streetman <email address hidden>  Mon, 09 Oct 2017 10:06:22 -0400

Available diffs

• diff from 3.2.5-5ubuntu4.3 to 3.2.5-5ubuntu4.4 (1.2 KiB)

mdadm (3.4-4ubuntu0.1) zesty; urgency=medium

  * Ship mdadm-shutdown.service and suggest dracut-core. Users of systemd
    with rootfs on Intel Matrix Raid and DDF external metadata-raid arrays
    that require mdmon monitoring, may wish to install dracut-core package
    and enable mdadm-shutdown.service. This will create a shutdown
    initramfs, that systemd-shutdown can pivot to. This may result in an
    improved shutdown behaviour with less hangs and synced raid
    arrays. The generated initramfs will takeover mdmon monitoring, wait
    for the arrays to be clean before stopping them and unmounting
    everything and finally executing requested shutdown command.
    LP: #1722491

 -- Dimitri John Ledkov <email address hidden>  Fri, 13 Oct 2017 18:31:49 +0100

Available diffs

• diff from 3.4-4 (in Debian) to 3.4-4ubuntu0.1 (1.6 KiB)

mdadm (4.0-2) unstable; urgency=medium

  * Ship mdadm-shutdown.service and suggest dracut-core. Users of systemd
    with rootfs on Intel Matrix Raid and DDF external metadata-raid arrays
    that require mdmon monitoring, may wish to install dracut-core package
    and enable mdadm-shutdown.service. This will create a shutdown
    initramfs, that systemd-shutdown can pivot to. This may result in an
    improved shutdown behaviour with less hangs and synced raid
    arrays. The generated initramfs will takeover mdmon monitoring, wait
    for the arrays to be clean before stopping them and unmounting
    everything and finally executing requested shutdown command.
  * Bump standards version, no changes required.
  * Bump debhelper to 9.
  * Add second email address to avoid NMU warnings.

 -- Dimitri John Ledkov <email address hidden>  Tue, 10 Oct 2017 11:55:52 +0100

Available diffs

• diff from 4.0-1 to 4.0-2 (1.7 KiB)

mdadm (3.3-2ubuntu7.5) xenial; urgency=medium

  * Add systemd shutdown script which waits for arrays to be clean during
    shutdown phase.
  * Do not take over initramfs mdmon services, and continue running them
    off initrd to avoid killing mdmon processes before systemd attempts dm
    detach and hang. As systemd in xenial does not appear to honor
    sendsigs.omit.d.
  * Add mdadm-shutdown.service which is recommended to be used on systems
    with Intel Matrix / DDF raid. It creates a shutdown initramfs which
    systemd-shutdown may pivot to, and complete clean external metadata
    raid array shutdown.
  * LP: #1722491

 -- Dimitri John Ledkov <email address hidden>  Mon, 09 Oct 2017 14:56:09 +0100

Available diffs

• diff from 3.3-2ubuntu7.4 to 3.3-2ubuntu7.5 (1.9 KiB)

mdadm (3.3-2ubuntu7.4) xenial; urgency=medium

  * Drop versioned dependency on initramfs-tools, which was only needed for
    upgrades and now keeps initramfs-tools installed on systems that don't
    need it.  LP: #1716818.
  * Guard calls to update-initramfs -u in the maintainer scripts for a
    check that the script is present.

 -- Steve Langasek <email address hidden>  Wed, 13 Sep 2017 03:52:18 +0000

Available diffs

• diff from 3.3-2ubuntu7.2 (in ~ci-train-ppa-service/ubuntu/2500-deletedppa) to 3.3-2ubuntu7.4 (931 bytes)
• diff from 3.3-2ubuntu7.3 to 3.3-2ubuntu7.4 (536 bytes)

mdadm (3.3-2ubuntu7.3) xenial; urgency=medium

  * Drop versioned dependency on initramfs-tools, which was only needed for
    upgrades and now keeps initramfs-tools installed on systems that don't
    need it.  LP: #1716818.
  * Guard calls to update-initramfs -u in the maintainer scripts for a
    check that the script is present.

 -- Steve Langasek <email address hidden>  Wed, 13 Sep 2017 03:52:18 +0000

Available diffs

• diff from 3.3-2ubuntu7.2 (in ~ci-train-ppa-service/ubuntu/2500-deletedppa) to 3.3-2ubuntu7.3 (703 bytes)

mdadm (4.0-1) unstable; urgency=medium

  * New upstream release. LP: #1668128
  * Drop warnings that raid arrays are missing from the initramfs
    configuration. Instead have a positive message as to which arrays are
    included in the initramfs.
  * Add a warning to mkconf generated file that mdadm.conf is copied into
    initrafms.
  * Fix checkarray script bugs. LP: #1599428 Closes: #787950 Closes: #843665

 -- Dimitri John Ledkov <email address hidden>  Thu, 22 Jun 2017 13:23:10 +0100

Available diffs

• diff from 3.4-4 to 4.0-1 (67.7 KiB)