Description of problem: Systemd starts fsck at every boot, ignoring /etc/fstab and ignoring partition check option (setted with tune2fs -i and/or -c) Version-Release number of selected component (if applicable): systemd-44-17.fc17 How reproducible: Start your system Steps to Reproduce: 1. Set the last value of /etc/fstab to "0" for root partition *and/or* use tune2fs -c 30 -i 30 /dev/sda2 (where sda2 is /) *and/or* disable fsck-root.service *and or* boot with fsck.mode=skip 2. Reboot 3. systemd-analyze plot > graph.svg Actual results: Disabling graphical boot it's possible to see fsck output. graph.svg shows fsck started on / and on /home Expected results: No fsck service started Additional info: 1. My hard drive is ok (according to SMART) 2. fsck is always reporting that my partitions are clean 3. From the rescue mode, I've tried many times to force fsck, but it didn't found any problem 4. The problem is always reproducible (I've rebooted many times with every kind of configuration: with and without initrd, using fsck.mode=skip with the last column of fstab set to zero, with tune2fs, with both tune2fs and fsck-root.service masked...)
Please attach a debug log (dmesg.txt) produced by following these instructions: http://freedesktop.org/wiki/Software/systemd/Debugging#If_You_Can_Get_a_Shell
Created attachment 598465 [details] Produced according to http://freedesktop.org/wiki/Software/systemd/Debugging#If_You_Can_Get_a_Shell
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
1. Set the last value of /etc/fstab to "0" for root partition Works for me. fstab-generator ignores lines with passno=0 in /etc/fstab and -.mount generated by fstab-generator is only thing that pull systemd-fsck-root.service in. 2. Use tune2fs -c 30 -i 30 /dev/sda2 (where sda2 is /) This is in the realm of /sbin/fsck.ext4 itself. 3. disable fsck-root.service You can mask it. 4. boot with fsck.mode=skip systemd-fsck program tests for this. In the boot log that you attached, systemd-fsck is run, but it exits quickly. There's nothign to suggest that it actually called fsck.ext4. I think that there's no bug here now. I haven't verified that nothing changed between 44 and now, but I don't think so. At least checking for fsck.skip looks exactly the same. Please reopen if something still doesn't work.