Change log for mdadm package in Ubuntu
1 → 50 of 157 results | First • Previous • Next • Last |
mdadm (4.3+20241108-1ubuntu1) plucky; urgency=medium * Merge with Debian unstable. Remaining changes (LP: #2089516): - d/*: Mount efivarfs during initramfs boot phase Add initramfs-tools script to mount efivarfs during initramfs boot phase (debian/local/initramfs-tools/init-top/00_mount_efivarfs) - d/* : Ship finalrd hook
Available diffs
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 <email address hidden> Mon, 29 Jul 2024 10:06:31 +0200
Available diffs
Superseded in plucky-release |
Published in oracular-release |
Deleted in oracular-proposed (Reason: Moved to oracular) |
mdadm (4.3+20240723-2ubuntu1) oracular; urgency=medium * Merge with Debian unstable. Remaining changes (LP: #2076403): - d/*: Mount efivarfs during initramfs boot phase Add initramfs-tools script to mount efivarfs during initramfs boot phase (debian/local/initramfs-tools/init-top/00_mount_efivarfs) - d/* : Ship finalrd hook * Dropped changes, no longer needed: - d/p/lp2069821/: mdadm: buffer overflow detected (LP #2069821) This patch has been integrated in mdadm upstream - d/p/lp2070371/: mdadm: wait for mdmon when it is started via systemd (LP #2070371) This patch has been integrated in mdadm upstream
Available diffs
mdadm (4.3+20240412-1ubuntu1) oracular; 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 * Dropped changes, no longer needed: - d/mdadm.maintscript: Ubuntu prior-versions dropped, not needed after 24.04
Available diffs
Superseded in oracular-release |
Published in noble-release |
Deleted in noble-proposed (Reason: Moved to noble) |
mdadm (4.3-1ubuntu2) noble; urgency=medium * No-change rebuild for CVE-2024-3094 -- Steve Langasek <email address hidden> Sun, 31 Mar 2024 09:17:46 +0000
Available diffs
- diff from 4.3-1ubuntu1 to 4.3-1ubuntu2 (313 bytes)
mdadm (4.3-1ubuntu1) noble; 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
Deleted in noble-updates (Reason: superseded by release) |
Superseded in noble-release |
Deleted in noble-proposed (Reason: Moved to noble) |
mdadm (4.2+20231121-1ubuntu1) noble; 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
mdadm (4.2+20231026-1ubuntu1) noble; 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
Superseded in noble-release |
Published in mantic-release |
Deleted in mantic-proposed (Reason: Moved to mantic) |
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
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)
Published in lunar-updates |
Superseded in mantic-release |
Deleted in mantic-proposed (Reason: Moved to mantic) |
Deleted in lunar-proposed (Reason: moved to -updates) |
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)
Superseded in mantic-release |
Published in lunar-release |
Deleted in lunar-proposed (Reason: Moved to lunar) |
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)
Superseded in lunar-release |
Obsolete in kinetic-release |
Deleted in kinetic-proposed (Reason: Moved to kinetic) |
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)
Superseded in kinetic-release |
Published in jammy-release |
Deleted in jammy-proposed (Reason: Moved to jammy) |
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)
Superseded in jammy-release |
Obsolete in impish-release |
Deleted in impish-proposed (Reason: Moved to impish) |
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
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)
Superseded in impish-release |
Obsolete in hirsute-release |
Deleted in hirsute-proposed (Reason: moved to Release) |
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)
Superseded in hirsute-release |
Obsolete in groovy-release |
Deleted in groovy-proposed (Reason: moved to Release) |
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)
Superseded in groovy-proposed |
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)
Superseded in focal-proposed |
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)
Superseded in groovy-release |
Published in focal-release |
Deleted in focal-proposed (Reason: moved to Release) |
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
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
Superseded in bionic-proposed |
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
Obsolete in disco-proposed |
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)
Superseded in eoan-proposed |
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)
Superseded in focal-release |
Obsolete in eoan-release |
Deleted in eoan-proposed (Reason: moved to release) |
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
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
Superseded in eoan-release |
Obsolete in disco-release |
Deleted in disco-proposed (Reason: moved to release) |
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)
Superseded in disco-release |
Obsolete in cosmic-release |
Deleted in cosmic-proposed (Reason: moved to release) |
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
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
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)
1 → 50 of 157 results | First • Previous • Next • Last |