Bug#929254: e2fsprogs: e2scrub cronjob spurious falure

2019-05-20 Thread Theodore Ts'o
merge 929186 929254
thanks

On Mon, May 20, 2019 at 04:53:29AM +0200, Marc Lehmann wrote:
> Package: e2fsprogs
> Version: 1.45.1-1
> Severity: normal
> 
> I just got this mail from cron:
> 
>So sorry, the automatic e2scrub of /db on host failed.
> 
>May 19 03:10:39 host systemd[1]: Starting Online ext4 Metadata Check for 
> /db...
>May 19 03:10:39 host e2scrub@-db[5246]: /db: Not connnected to a LVM 
> logical volume.
>May 19 03:10:39 host e2scrub@-db[5246]: Usage: /sbin/e2scrub [OPTIONS] 
> mountpoint | device

There is a fix coming soon; my apologies for this regression!

> (And, a very minor typo, it should be "an LVM", not "a LVM")

Good point, thanks.

- Ted



Bug#929254: e2fsprogs: e2scrub cronjob spurious falure

2019-05-19 Thread Marc Lehmann
Package: e2fsprogs
Version: 1.45.1-1
Severity: normal

I just got this mail from cron:

   So sorry, the automatic e2scrub of /db on host failed.

   May 19 03:10:39 host systemd[1]: Starting Online ext4 Metadata Check for 
/db...
   May 19 03:10:39 host e2scrub@-db[5246]: /db: Not connnected to a LVM logical 
volume.
   May 19 03:10:39 host e2scrub@-db[5246]: Usage: /sbin/e2scrub [OPTIONS] 
mountpoint | device
   May 19 03:10:39 host e2scrub@-db[5246]: mountpoint must be on a LVM-managed 
block device
   May 19 03:10:39 host e2scrub@-db[5246]: -n: Show what commands e2scrub would 
execute.
   May 19 03:10:39 host e2scrub@-db[5246]: -r: Remove e2scrub snapshot and 
exit, do not check anything.
   May 19 03:10:39 host e2scrub@-db[5246]: -t: Run fstrim if successful.
   May 19 03:10:39 host e2scrub@-db[5246]: -V: Print version information and 
exit.
   May 19 03:10:41 host systemd[1]: e2scrub@-db.service: Main process exited, 
code=exited, status=1/FAILURE
   May 19 03:10:41 host systemd[1]: e2scrub@-db.service: Failed with result 
'exit-code'.
   May 19 03:10:41 host systemd[1]: Failed to start Online ext4 Metadata Check 
for /db.
   May 19 03:10:41 host systemd[1]: e2scrub@-db.service: Triggering OnFailure= 
dependencies.

Indeed, running e2scrub on /db manually gives the above output, which is
actually correct, as /db is on a dmcrypt device which in turn is on an
lvm device.

I think either the cron job should not run automatically, or this type of
error should be silently ignored.

Also, the documentation for the failing e2scrub@.service unit only refers
"man:e2scrub(8)" which says nothing about the service (or how to disable
it), as far as I can see.

(And, a very minor typo, it should be "an LVM", not "a LVM")

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 4.19.27-041927-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcom-err2  1.45.1-1
ii  libext2fs2   1.45.1-1
ii  libss2   1.44.5-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
pn  e2fsprogs-l10n  

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
pn  fuse2fs
ii  gpart  1:0.3-6
ii  parted 3.2-25

-- no debconf information