Package: e2fsprogs
Version: 1.42.13-1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
using systemd, fsck takes too much time, so systemd is giving up
* What exactly did you do (or not do) that was effective (or
ineffective)?
using systemd?
* What was the outcome of this action?
fs is corrupted
* What outcome did you expect instead?
systemd should be waiting until fsck finishes
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable-updates'),
(500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 4.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages e2fsprogs depends on:
ii e2fslibs 1.42.13-1
ii libblkid1 2.27.1-1
ii libc6 2.19-22
ii libcomerr2 1.42.13-1
ii libss2 1.42.13-1
ii libuuid1 2.27.1-1
ii util-linux 2.27.1-1
e2fsprogs recommends no packages.
Versions of packages e2fsprogs suggests:
pn e2fsck-static <none>
pn gpart <none>
ii parted 3.2-10
-- no debconf information
[ 135.640989] EXT4-fs (sdc3): mounting ext2 file system using the ext4
subsystem
[ 135.670994] EXT4-fs (sdc3): warning: mounting unchecked fs, running e2fsck
is recommended
[ 135.793096] EXT4-fs (sdc3): mounted filesystem without journal. Opts: (null)
