On 28/02/2019 09.45, Felix Miata wrote:
Carlos E.R. composed on 2019-02-22 13:01 (UTC+0100):
Felix Miata wrote:
The question remaining is what next to do? .. systemctl status fstrim
# systemctl status fstrim â fstrim.service - Discard unused blocks Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2019-02-25 00:00:00 EST; 3 days ago Process: 25267 ExecStart=/usr/sbin/fstrim -av (code=exited, status=0/SUCCESS) Main PID: 25267 (code=exited, status=0/SUCCESS)
/usr/lib/systemd/system/fstrim.timer # systemctl status fstrim.timer â fstrim.timer - Discard unused blocks once a week Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled) Active: active (waiting) since Fri 2019-02-22 02:42:04 EST; 6 days ago Docs: man:fstrim
This seems to be the same that I have
grep -i "discard\|trim" /var/log/messages # grep -i "discard\|trim" /var/log/messages
grep: /var/log/messages: No such file or directory #
or
journalctl | grep -i "discard\|trim # journalctl | grep -i "discard\|trim" ... Aug 31 16:31:20 myhost nmbd[1465]: process_lanman_packet: Discarding datagram from IP 192.168.###.###. Source name myhost<00> is one of our names ! # journalctl | grep -i "discard\|trim" | wc -l 2954 # journalctl | grep -i "discard\|trim" | grep -v lanman #
But the absence of entries in log is strange. I would try to run it manually and see: fstrim -av -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)