Carlos E. R. composed on 2019-02-28 12:07 (UTC+0100):
Felix Miata wrote:
> Carlos E.R. composed on 2019-02-22 13:01
Felix Miata wrote:
>>> The question remaining is what next to
>> systemctl status fstrim
> # systemctl status fstrim
> â fstrim.service - Discard unused blocks
> Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static; vendor preset:
> 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)
> # systemctl status fstrim.timer
> â fstrim.timer - Discard unused blocks once a week
> Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor preset:
> 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"
> # grep -i "discard\|trim" /var/log/messages
> grep: /var/log/messages: No such file or directory
>> journalctl | grep -i "discard\|trim
> # journalctl | grep -i "discard\|trim"
> Aug 31 16:31:20 myhost nmbd: process_lanman_packet: Discarding datagram from
> 192.168.###.###. Source name myhost<00> is one of our names !
> # journalctl | grep -i "discard\|trim" | wc -l
> # 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
/disks/boot: 0 B (0 bytes) trimmed
/: 0 B (0 bytes) trimmed
I've emailed PNY, and ordered another brand.
I could slip this in as is right now
but its my only backup and it's over 6 months old. With the current as tenous as it
is I hesitate
to risk its current content by trying clone over it from the current.
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org