Re: [PATCH] fstrim: add systemd units

["Thomas Bächler" <thomas@archlinux.org>]

[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]

Am 09.04.2014 14:12, schrieb Ruediger Meier:
>> well, "fstrim -a" contains heruistic to select the right filestems
>> (it really does not call trim for all devices), it has been
>> implemented to *avoid* sysadmins creativity. If you don't like it,
>> you can use "fstrim <device>" (for example from crontab).
> 
> I'd like the documentation more detailed.
> Does it really run on all mounts or only /etc/fstab?
> Does it write on automounted devices which are probably not owned by the 
> admin? Does it affect read-only mounts?

The documentation is precise here:

'Trim all mounted filesystems on devices that support the discard
operation.'

It says exactly what it will do. Every one of your questions is answered.

> IMO the task itself is already installed since we have fstrim's 
> option -a". You just need to _enable_ it to run whenever you want for 
> example by using crontab. That's trivial.

Because it takes time. I have done it four times already and it cost me
several minutes each time. Now nobody has to do it again.

> Nobody would have thought about adding a 1-liner cronjob file to 
> util-linux eventhough any distro has /etc/cron.daily/. But now systemd 
> timer? Thats what I don't understand.

I don't know why nobody thought about doing that in the past, maybe
nobody cared about the needs of all those other admins. Maybe because
installing a file into cron.daily automatically enables it. Maybe
because nobody cared about anything but his own system?

> If _creating_ a systemd timer is too complicated for today's admins

It is not complicated, it is just a task that shouldn't be repeated
countless times.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]