View Single Post
Staro 11.03.2021., 23:01   #1024
c-shadow
Premium
Moj komp
 
c-shadow's Avatar
 
Datum registracije: Feb 2007
Lokacija: Istra
Postovi: 3,464
Citiraj:
Autor domy_os Pregled postova
Pa zar nemaš weekly crontab task za TRIM? Imao sam ga na Mintu, imam ga i sad na Fedori. Ili mislimo na nešto drugo?

EDIT: Zapravo nije crontab nego systemd timer...

Code:
[domy@Domy-NB etc]$ 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 Tue 2021-03-02 17:46:58 CET; 1 weeks 2 days ago
    Trigger: Mon 2021-03-15 01:07:20 CET; 3 days left
   Triggers: ● fstrim.service
       Docs: man:fstrim

ožu 02 17:46:58 Domy-NB systemd[1]: Started Discard unused blocks once a week.
Imam, ali iz nekog razloga se to pokretalo i na svakom bootu što ja nisam znao. A nisam niti očekivao da traje tako dugo.


EDIT:
I dalje jubuntu pokreće trim na svakom bootu.
Ovo je isti komp, s Crucial MX, samo to nije problem jer traje 10s, a ne 10 min kao sa starom Adatom. Kako je stroj upaljen 24/7 ne zamaram se time ali dobro je znati

Code:
uptime
 07:01:33 up 34 days, 17:09,  2 users,  load average: 0,72, 0,87, 0,75

 systemd-analyze blame
          11.503s fstrim.service
          3.138s NetworkManager-wait-online.service
          2.222s sendmail.service
          1.257s nfs-server.service
           696ms media-multimedia-swapfile.swap
           674ms dev-sda1.device
           465ms udisks2.service
           435ms vboxdrv.service
           374ms plymouth-quit-wait.service
Systemd timer uredno radi:
Code:
journalctl -u fstrim
-- Logs begin at Wed 2018-10-24 17:53:32 CEST, end at Fri 2021-03-12 07:00:01 CET. --
velj 01 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
velj 01 00:00:10 witch64 fstrim[17846]: /: 16,2 GiB (17413054464 bytes) trimmed
velj 01 00:00:10 witch64 systemd[1]: Started Discard unused blocks.
-- Reboot --
velj 08 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
velj 08 00:00:31 witch64 fstrim[3896]: /: 385 GiB (413389037568 bytes) trimmed
velj 08 00:00:31 witch64 systemd[1]: Started Discard unused blocks.
velj 15 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
velj 15 00:00:11 witch64 fstrim[12679]: /: 18,5 GiB (19819356160 bytes) trimmed
velj 15 00:00:11 witch64 systemd[1]: Started Discard unused blocks.
velj 22 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
velj 22 00:00:08 witch64 fstrim[2467]: /: 13,4 GiB (14421602304 bytes) trimmed
velj 22 00:00:08 witch64 systemd[1]: Started Discard unused blocks.
ožu 01 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
ožu 01 00:00:12 witch64 fstrim[19984]: /: 18,4 GiB (19718438912 bytes) trimmed
ožu 01 00:00:12 witch64 systemd[1]: Started Discard unused blocks.
ožu 08 00:00:01 witch64 systemd[1]: Starting Discard unused blocks...
ožu 08 00:00:13 witch64 fstrim[11994]: /: 23,9 GiB (25658396672 bytes) trimmed
ožu 08 00:00:13 witch64 systemd[1]: Started Discard unused blocks.
Dokumentirano, ali nisam izguglao neko rješenje. Naravno uvijek se može isključiti ono govno od systemd i staviti fstrim u klasični cron.
https://askubuntu.com/questions/1165...high-boot-time
https://forums.linuxmint.com/viewtopic.php?t=289947

Zadnje izmijenjeno od: c-shadow. 12.03.2021. u 07:04.
c-shadow je offline   Reply With Quote