[ubuntu/impish-proposed] mdadm 4.1-11ubuntu1 (Accepted)
Balint Reczey
rbalint at ubuntu.com
Tue May 11 13:53:12 UTC 2021
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.
Date: Tue, 11 May 2021 15:49:35 +0200
Changed-By: Balint Reczey <rbalint at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/+source/mdadm/4.1-11ubuntu1
-------------- next part --------------
Format: 1.8
Date: Tue, 11 May 2021 15:49:35 +0200
Source: mdadm
Architecture: source
Version: 4.1-11ubuntu1
Distribution: impish
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Balint Reczey <rbalint at ubuntu.com>
Closes: 962844
Changes:
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.
Checksums-Sha1:
0e1c4f0367af2d08f7a8a8ac8197136d79d6337a 2092 mdadm_4.1-11ubuntu1.dsc
b1c2f380e3afe2e0337ad9ec077d747226156600 105644 mdadm_4.1-11ubuntu1.debian.tar.xz
6332166c2756fbb57bc9672bd1cbeac171ebf173 7248 mdadm_4.1-11ubuntu1_source.buildinfo
Checksums-Sha256:
2587b3e242034f75d7f760c9d25a12371e7d2ca323331e0dc64dbeb8955cf4ed 2092 mdadm_4.1-11ubuntu1.dsc
f90bad3d487d1393fe36e9891fe7ae875c3316d09c95def3a848ddc2ff21c8ee 105644 mdadm_4.1-11ubuntu1.debian.tar.xz
45626739d2c1ced9b470b15b63758105b9942cf1e6d808c0e9ae67fd3aef97cc 7248 mdadm_4.1-11ubuntu1_source.buildinfo
Files:
f8405a365830d3019d6d3ecfd3efb357 2092 admin optional mdadm_4.1-11ubuntu1.dsc
f797574d97e1c785a0dc8546f46379f1 105644 admin optional mdadm_4.1-11ubuntu1.debian.tar.xz
47308ff95497f93ef18d7c370d8d9456 7248 admin optional mdadm_4.1-11ubuntu1_source.buildinfo
Original-Maintainer: Felix Lechner <felix.lechner at lease-up.com>
More information about the impish-changes
mailing list