Change logs for mdadm source package in Focal

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.

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>  Mon, 28 Sep 2020 12:29:11 -0400

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

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.

mdadm (4.1-5) unstable; urgency=medium

  * QA upload.
  * Fix cross-compilation failure. (Closes: #866522).
    Thanks to Helmut Grohne.
  * Add support for raid0/linear 'broken' state. (Closes: #943520).
    Thanks to Guilherme G. Piccoli and Dan Streetman. LP: #1847924.

 -- dann frazier <email address hidden>  Thu, 23 Jan 2020 11:41:55 -0700

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

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