On Fri, 20 Sep 2019 18:51:37 -0400 Theodore Y. Ts'o wrote: > On Fri, Sep 20, 2019 at 11:40:30PM +0200, Francesco Poli wrote: > > > > Hello Thorsten, hello Theodore, > > I am another user who began receiving the same error messages from cron > > on a box with LVM, but without systemd. > > It's only going to happen if you aren't using systemd, since if you > are using systemd, e2scrub_all gets run out of a systemd timer unit > file. The cron job is the fallback which is only used on non-systemd > systems.
Sure, that's clear. > > > While waiting for a more radical fix (in cron or in lvm), do you think > > this workaround should be included in the next Debian revision of > > e2fsprogs? > > Yes, this will be in the next revision of e2fsprogs. Good, thanks for taking care of this! > It's unclear if > this is serious enough bug to justify an update to Debian stable > (that's up to the release managers, not me). It will be in the > release of Debian testing and Debian backports, however. I think that will suffice, at least as far as I am personally concerned. Thank you so much for your kind reply. Bye. -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpQJiyBzaSS6.pgp
Description: PGP signature
