| Summary: | fsck runs on every boot and ignores fsck.mode parameter | ||
|---|---|---|---|
| Product: | systemd | Reporter: | Jani Rahkola <jani.rahkola> |
| Component: | general | Assignee: | systemd-bugs |
| Status: | RESOLVED WORKSFORME | QA Contact: | systemd-bugs |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=840298 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
dmesg with systemd.log_level=debug
kernel command-line fstab /var/log/messages.log systemctl dump systemd-analyze plot of the boot |
||
Created attachment 65082 [details]
kernel command-line
Created attachment 65083 [details]
fstab
Created attachment 65084 [details]
/var/log/messages.log
Created attachment 65085 [details]
systemctl dump
Created attachment 65086 [details]
systemd-analyze plot of the boot
Works for me. At least after the recent changes to systemd-fstab-generator. Please note that if fsck.mode=skip is given, systemd-fsck is executed but simply exits immediately. Please reopen if something still doesn't work. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 65081 [details] dmesg with systemd.log_level=debug fsck runs on every boot for all filesystems. Setting the fsck.mode kernel parameter to skip has no effect.