This is fixed by e2fsprogs 1.45.1-3 in Debian, or in the soon to be
released e2fsprogs 1.45.2.
e2fsprogs (1.45.1-3) unstable; urgency=medium
* Fix e2scrub_all cron failures (Closes: #9292870)
-- Theodore Y. Ts'o <ty...@mit.edu> Mon, 20 May 2019 21:48:40 -0400
e2fsprogs (1.45.1-2) unstable; urgency=medium
* Avoid spurious e2scrub_all error messages spamming administrators from
cron/systemd timer units when lvm2 is not installed and/or there are
no lvm devices present in the system (Closes: #928977, #929186, #929254)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1830500
Title:
Issue with e2scrub@-.service and e2scrub@-boot.service which tries to
scrub ext4 partitions (/boot and /)
Status in e2fsprogs package in Ubuntu:
Confirmed
Bug description:
This is a fresh install of 19.04 upgraded to 19.10.
I'm receiving these emails which seems to be related to a cronjob.
I also tried to run /usr/sbin/e2scrub_all manually and I'm receiving the 2
same emails after I ran it.
The emails in question:
So sorry, the automatic e2scrub of /boot on cryptosid.local.lan
failed.
A log of what happened follows:
● e2scrub@-boot.service - Online ext4 Metadata Check for /boot
Loaded: loaded (/lib/systemd/system/e2scrub@.service; static; vendor preset:
enabled)
Active: failed (Result: exit-code) since Fri 2019-05-24 08:26:37 EDT; 73ms ago
Docs: man:e2scrub(8)
Process: 28530 ExecStart=/sbin/e2scrub -t /boot (code=exited,
status=1/FAILURE)
Main PID: 28530 (code=exited, status=1/FAILURE)
May 24 08:26:35 CryptoSiD systemd[1]: Starting Online ext4 Metadata Check for
/boot...
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: /boot: Not connnected to a
LVM logical volume.
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: Usage: /sbin/e2scrub
[OPTIONS] mountpoint | device
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: mountpoint must be on a
LVM-managed block device
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: -n: Show what commands
e2scrub would execute.
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: -r: Remove e2scrub snapshot
and exit, do not check anything.
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: -t: Run fstrim if successful.
May 24 08:26:35 CryptoSiD e2scrub@-boot[28530]: -V: Print version information
and exit.
May 24 08:26:37 CryptoSiD systemd[1]: e2scrub@-boot.service: Main process
exited, code=exited, status=1/FAILURE
May 24 08:26:37 CryptoSiD systemd[1]: e2scrub@-boot.service: Failed with
result 'exit-code'.
May 24 08:26:37 CryptoSiD systemd[1]: Failed to start Online ext4 Metadata
Check for /boot.
May 24 08:26:37 CryptoSiD systemd[1]: e2scrub@-boot.service: Triggering
OnFailure= dependencies.
So sorry, the automatic e2scrub of /boot on cryptosid.local.lan
failed.
A log of what happened follows:
● e2scrub@-boot.service - Online ext4 Metadata Check for /boot
Loaded: loaded (/lib/systemd/system/e2scrub@.service; static; vendor preset:
enabled)
Active: failed (Result: exit-code) since Thu 2019-05-23 23:09:29 EDT; 163ms
ago
Docs: man:e2scrub(8)
Process: 31843 ExecStart=/sbin/e2scrub -t /boot (code=exited,
status=1/FAILURE)
Main PID: 31843 (code=exited, status=1/FAILURE)
May 23 23:09:27 CryptoSiD systemd[1]: Starting Online ext4 Metadata Check for
/boot...
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: /boot: Not connnected to a
LVM logical volume.
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: Usage: /sbin/e2scrub
[OPTIONS] mountpoint | device
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: mountpoint must be on a
LVM-managed block device
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: -n: Show what commands
e2scrub would execute.
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: -r: Remove e2scrub snapshot
and exit, do not check anything.
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: -t: Run fstrim if successful.
May 23 23:09:27 CryptoSiD e2scrub@-boot[31843]: -V: Print version information
and exit.
May 23 23:09:29 CryptoSiD systemd[1]: e2scrub@-boot.service: Main process
exited, code=exited, status=1/FAILURE
May 23 23:09:29 CryptoSiD systemd[1]: e2scrub@-boot.service: Failed with
result 'exit-code'.
May 23 23:09:29 CryptoSiD systemd[1]: Failed to start Online ext4 Metadata
Check for /boot.
May 23 23:09:29 CryptoSiD systemd[1]: e2scrub@-boot.service: Triggering
OnFailure= dependencies.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: e2fsprogs 1.45.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.11-0ubuntu2
Architecture: amd64
Date: Sat May 25 17:43:20 2019
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1830500/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
