This bug was fixed in the package mdadm - 4.1-4ubuntu1 --------------- 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 <da...@ubuntu.com> Wed, 04 Dec 2019 07:05:07 -0700 ** Changed in: mdadm (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850540 Title: multi-zone raid0 corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1850540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs