Question about fstrim.service which failed once a week

After login motd told me that fstrim.service failed:

● fstrim.service - Discard unused blocks on filesystems from /etc/fstab
     Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2020-08-03 00:00:01 UTC; 5 days ago
TriggeredBy: ● fstrim.timer
       Docs: man:fstrim(8)
    Process: 922065 ExecStart=/usr/sbin/fstrim --fstab --verbose --quiet (code=exited, status=32)
   Main PID: 922065 (code=exited, status=32)

8月 03 00:00:00 stl02.svr.anislet.dev systemd[1]: Starting Discard unused blocks on filesystems from /etc/fstab...
8月 03 00:00:01 stl02.svr.anislet.dev fstrim[922065]: fstrim: failed to parse /etc/fstab: No such file or directory
8月 03 00:00:01 stl02.svr.anislet.dev systemd[1]: fstrim.service: Main process exited, code=exited, status=32/n/a
8月 03 00:00:01 stl02.svr.anislet.dev systemd[1]: fstrim.service: Failed with result 'exit-code'.
8月 03 00:00:01 stl02.svr.anislet.dev systemd[1]: Failed to start Discard unused blocks on filesystems from /etc/fstab.

Fedora CoreOS don’t have a fstab file cause it use systemd mount file. as fstrim.timer said this service will exec once a week.

So why don’t you just disable this timer or is there a reason to keep this timer enable?

1 Like

Hi @Orwill. Please see https://github.com/coreos/fedora-coreos-tracker/issues/468

1 Like