Pierre Willaime writes:
Thanks all. I activated `# systemctl enable fstrim.timer` (thanks Linux-Fan).
You're welcome :)
But I do not think my issue is trim related after all. I have always a lot of I/O activities from jdb2 even just after booting and even when the computer is doing nothing for hours.Here is an extended log of iotop where you can see jdb2 anormal activities: https://pastebin.com/eyGcGdUz
According to that, a lot of firefox-esr and dpkg and some thunderbird processes are active. Is there a high intensity of I/O operations when all Firefox, Thunderbird instances and system upgrades are closed?
When testing with iotop here, options `-d 10 -P` seemed to help getting a steadier and less cluttered view. Still, filtering your iotop output for Firefox, Thunderbird and DPKG respectively seems to be quite revealing:
| $ grep firefox-esr eyGcGdUz | grep -E '[0-9]{4,}.[0-9]{2} K/s'
| 10:38:51 3363 be/4 pierre 0.00 K/s 1811.89 K/s 0.00 % 17.64 % firefox-esr [mozStorage #3]
| 10:39:58 5117 be/4 pierre 0.00 K/s 1112.59 K/s 0.00 % 0.37 % firefox-esr [IndexedDB #14]
| 10:41:55 3363 be/4 pierre 0.00 K/s 6823.06 K/s 0.00 % 0.00 % firefox-esr [mozStorage #3]
| 10:41:55 3305 be/4 pierre 1469.88 K/s 0.00 K/s 0.00 % 60.57 % firefox-esr [QuotaManager IO]
| 10:41:55 3363 be/4 pierre 6869.74 K/s 6684.07 K/s 0.00 % 31.96 % firefox-esr [mozStorage #3]
| 10:41:56 6752 be/4 pierre 2517.19 K/s 0.00 K/s 0.00 % 99.99 % firefox-esr [Indexed~Mnt #13]
| 10:41:56 6755 be/4 pierre 31114.18 K/s 0.00 K/s 0.00 % 99.58 % firefox-esr [Indexed~Mnt #16]
| 10:41:56 3363 be/4 pierre 9153.40 K/s 0.00 K/s 0.00 % 87.06 % firefox-esr [mozStorage #3]
| 10:41:57 6755 be/4 pierre 249206.18 K/s 0.00 K/s 0.00 % 59.01 % firefox-esr [Indexed~Mnt #16]
| 10:41:57 6755 be/4 pierre 251353.11 K/s 0.00 K/s 0.00 % 66.02 % firefox-esr [Indexed~Mnt #16]
| 10:41:58 6755 be/4 pierre 273621.58 K/s 0.00 K/s 0.00 % 59.51 % firefox-esr [Indexed~Mnt #16]
| 10:41:58 6755 be/4 pierre 51639.70 K/s 0.00 K/s 0.00 % 94.90 % firefox-esr [Indexed~Mnt #16]
| 10:41:59 6755 be/4 pierre 113869.64 K/s 0.00 K/s 0.00 % 79.03 % firefox-esr [Indexed~Mnt #16]
| 10:41:59 6755 be/4 pierre 259549.09 K/s 0.00 K/s 0.00 % 56.99 % firefox-esr [Indexed~Mnt #16]
| 10:44:41 3265 be/4 pierre 1196.21 K/s 0.00 K/s 0.00 % 20.89 % firefox-esr
| 10:44:41 3289 be/4 pierre 3813.36 K/s 935.22 K/s 0.00 % 4.59 % firefox-esr [Cache2 I/O]
| 10:44:53 3363 be/4 pierre 0.00 K/s 1176.90 K/s 0.00 % 0.00 % firefox-esr [mozStorage #3]
| 10:49:28 3363 be/4 pierre 0.00 K/s 1403.16 K/s 0.00 % 0.43 % firefox-esr [mozStorage #3]
So there are incredible amounts of data being read by Firefox (Gigabytes in
a few minutes)? Does this load reflect in atop or iotop's summarizing lines
at the begin of the respective screens?
| $ grep thunderbird eyGcGdUz | grep -E '[0-9]{4,}.[0-9]{2} K/s'
| 10:38:43 2846 be/4 pierre 0.00 K/s 1360.19 K/s 0.00 % 15.51 % thunderbird [mozStorage #1]
| 10:39:49 2873 be/4 pierre 0.00 K/s 4753.74 K/s 0.00 % 0.00 % thunderbird [mozStorage #6]
| 10:39:49 2875 be/4 pierre 0.00 K/s 19217.56 K/s 0.00 % 0.00 % thunderbird [mozStorage #7]
| 10:39:50 2883 be/4 pierre 0.00 K/s 18014.56 K/s 0.00 % 29.39 % thunderbird [mozStorage #8]
| 10:39:50 2883 be/4 pierre 0.00 K/s 3305.94 K/s 0.00 % 27.28 % thunderbird [mozStorage #8]
| 10:39:51 2883 be/4 pierre 0.00 K/s 61950.19 K/s 0.00 % 63.11 % thunderbird [mozStorage #8]
| 10:39:51 2883 be/4 pierre 0.00 K/s 41572.77 K/s 0.00 % 27.19 % thunderbird [mozStorage #8]
| 10:39:52 2883 be/4 pierre 0.00 K/s 20961.20 K/s 0.00 % 65.02 % thunderbird [mozStorage #8]
| 10:39:52 2883 be/4 pierre 0.00 K/s 43345.16 K/s 0.00 % 0.19 % thunderbird [mozStorage #8]
| 10:42:27 2846 be/4 pierre 0.00 K/s 1189.63 K/s 0.00 % 0.45 % thunderbird [mozStorage #1]
| 10:42:33 2846 be/4 pierre 0.00 K/s 1058.52 K/s 0.00 % 0.31 % thunderbird [mozStorage #1]
| 10:47:27 2846 be/4 pierre 0.00 K/s 2113.53 K/s 0.00 % 0.66 % thunderbird [mozStorage #1]
Thunderbird seems to write a lot here. This would average at ~18 MiB/s of writing
and hence explain why the SSD is loaded continuously. Again: Does it match the
data reported by atop? [I am not experienced in reading iotop output, hence
I might interpret the data wrongly].
By comparison, dpkg looks rather harmless:
| $ grep dpkg eyGcGdUz | grep -E '[0-9]{4,}.[0-9]{2} K/s'
| 10:38:25 4506 be/4 root 0.00 K/s 4553.67 K/s 0.00 % 0.26 % dpkg --status-fd 23 --no-triggers --unpack --auto-deconfigure --force-remove-protected --recursive /tmp/apt-dpkg-install-E69bfZ
| 10:38:33 4506 be/4 root 7.73 K/s 4173.77 K/s 0.00 % 1.52 % dpkg --status-fd 23 --no-triggers --unpack --auto-deconfigure --force-remove-protected --recursive /tmp/apt-dpkg-install-E69bfZ
| 10:38:49 4506 be/4 root 7.74 K/s 3770.01 K/s 0.00 % 1.41 % dpkg --status-fd 23 --no-triggers --unpack --auto-deconfigure --force-remove-protected --recursive /tmp/apt-dpkg-install-E69bfZ
| 10:39:01 4506 be/4 root 0.00 K/s 5529.57 K/s 0.00 % 5.85 % [dpkg]
| 10:39:29 4664 be/4 root 0.00 K/s 5480.00 K/s 0.00 % 3.43 % dpkg --status-fd 23 --configure --pending
This would explain that you are seeing slow progress...
[...]
HTH
Linux-Fan
öö
Attachment:
pgpz2Gue_TcA6.pgp
Description: PGP signature