[systemd-devel] systemd-fsck doesn't check data partiton

[Benjamin Beckmeyer]

Hi all,
we have a problem on an embedded device wit emmc with systemd-fsck. It just doesn't 
check the partition. The exit status 8 means the partition is mounted, because when 
I do a check on the live system I get the same error. 

 root at em-switch:~ systemctl status systemd-fsck*
● systemd-fsck at dev-disk-by\x2duuid-1073706a\x2da8c1\x2d4d59\x2db701\x2d73b07f603
   Loaded: loaded (/usr/lib/systemd/system/systemd-fsck at .service; static; vendor
   Active: active (exited) since Sat 2018-12-01 01:00:07 CET; 2min 3s ago
     Docs: man:systemd-fsck at .service(8)
  Process: 210 ExecStart=/usr/lib/systemd/systemd-fsck /dev/disk/by-uuid/1073706
 Main PID: 210 (code=exited, status=0/SUCCESS)

Dec 01 01:00:07 em-switch systemd[1]: Starting File System Check on /dev/disk/by
Dec 01 01:00:07 em-switch systemd-fsck[210]: read_bad_blocks_file: No such file 
Dec 01 01:00:07 em-switch systemd-fsck[210]: fsck failed with exit status 8.
Dec 01 01:00:07 em-switch systemd-fsck[210]: Ignoring error.
Dec 01 01:00:07 em-switch systemd[1]: Started File System Check on /dev/disk/by-

root at em-switch:~ systemctl --version
systemd 239
-PAM -AUDIT -SELINUX -IMA -APPARMOR -SMACK -SYSVINIT -UTMP -LIBCRYPTSETUP -GCRYPT 
-GNUTLS -ACL -XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 -IDN -PCRE2 
default-hierarchy=hybrid

The embedded device has 3 partitions. 2 rootfs(ro) and one data partition(rw), 
between the rootfs we could do updates so we have everytime one partition to 
fallback if something got wrong. 

systemd-journald is writing its log to /data/journal and is configured to 
store=persistent.

/etc/fstab:
*/ snip
UUID=1073706a-a8c1-4d59-b701-73b07f603c4c /data ext4 defaults,sync 0 2
/data/journal /var/log none bind 0 0

I'm asking because we get some crazy write errors on the ext4 data partition. 
and the system won't boot anymore. After I boot the system from SD card and 
do a e2fsck on the data partition, the system will run again witho errors.

Hopefully you can help me with this error, I will write to the ext4 mailing 
list for the error messages too but let me know if you need some more information.

Best regards,
Benjamin Beckmeyer