[Bug 1608880] Re: systemd doesnt work with timed fsck, only with counted mount fsck

2021-06-30 Thread Dan Streetman
please reopen if this is still an issue ** Changed in: systemd (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1608880 Title: systemd doesnt work with t

[Bug 1608880] Re: systemd doesnt work with timed fsck, only with counted mount fsck

2017-01-19 Thread Reuben Thomas
I confirm this problem. Another curious thing is that fsck appears to be run, but doesn't do anything as the file system is clean: /run/initramfs/fsck.log says: Log of fsck -C -a -T -t ext4 /dev/md1 Thu Jan 19 19:09:43 2017 /dev/md1: clean, 46950805/57753600 files, 197262216/231002624 blocks T

[Bug 1608880] Re: systemd doesnt work with timed fsck, only with counted mount fsck

2016-10-19 Thread Nils Kassube
I can confirm this bug. However /forcefsck seems not to be supported because it isn't mentioned in the man page. When I log in to one of the 16.04 systems, I get this info: *** /dev/sda5 will be checked for errors at next reboot *** But the command "dmesg|grep -i e2fsck" gives this output: [ 1