mdadm 4.1-11ubuntu1 source package in Ubuntu

Changelog

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

mdadm (4.1-11) unstable; urgency=medium

  * Load efivars module in initramfs, if available. (Closes: #962844)
  * Do not explicitly include /bin/rm in initramfs; /usr/bin/rm
    is already present. (See: #875918)
  * Bump Standards-Version to 4.5.1.

 -- Balint Reczey <email address hidden>  Tue, 11 May 2021 15:49:35 +0200

Upload details

Uploaded by:
Balint Reczey
Uploaded to:
Impish
Original maintainer:
Ubuntu Developers
Architectures:
linux-any
Section:
admin
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
mdadm_4.1.orig.tar.gz 569.9 KiB c4f1a001ed9a24a701897ee17a0ccf27ba772a8a05871ae9b1415308ff82406b
mdadm_4.1-11ubuntu1.debian.tar.xz 103.2 KiB f90bad3d487d1393fe36e9891fe7ae875c3316d09c95def3a848ddc2ff21c8ee
mdadm_4.1-11ubuntu1.dsc 2.0 KiB 2587b3e242034f75d7f760c9d25a12371e7d2ca323331e0dc64dbeb8955cf4ed

Available diffs

View changes file

Binary packages built by this source

mdadm: No summary available for mdadm in ubuntu impish.

No description available for mdadm in ubuntu impish.

mdadm-dbgsym: No summary available for mdadm-dbgsym in ubuntu impish.

No description available for mdadm-dbgsym in ubuntu impish.