There used to be nearly 3.5G on / before I recently upgraded from 13.2 to Tumbleweed but somehow now it is much more filled although no new packages were added and it seems Tumblweed updates keep adding more and more with each update.
I notice that /var/log/journal is nearly 900mb. Is it possible this log to be rotated via logrotate? If yes - how? No idea if there is anything to clean in /usr.
What would you suggest in order to prevent disaster of filling the root partition too much? This is an old laptop which works well but I cannot invest in upgrading it, just willing to use it as long as it is alive.
No, it is controlled by journald directly. Look at “man journald.conf” for various settings to control total journal size.
If you updated, you probably also have some syslog daemon running, in which case you effectively have most logs twice. You may consider either to remove syslog or to disable persistent journal completely (Storage=none) to avoid duplication. You may need to manually clean /var/log/journal after setting Storage=none (and rebooting/restarting journald).
Do you by any chance have another small HD that you could add as a 2nd drive and use for the /home partition? 8 Gigs is terribly small for a Tumbleweed partition.
If you updated, you probably also have some syslog daemon running, in which case you effectively have most logs twice. You may consider either to remove syslog or to disable persistent journal completely (Storage=none) to avoid duplication. You may need to manually clean /var/log/journal after setting Storage=none (and rebooting/restarting journald).
I have been trying to figure that out but I couldn’t. How do I check if there is such thing as syslog at all and disable it? Also is there any negative impact in doing that or just staying with journald is enough?
I don’t have another small HD. This laptop is very old and I don’t see any point in upgrading it at all. But it works fine for what it is used for.
Understood. And, oh, I did not notice earlier that it was a laptop, which would probably mean that you could only use an external drive, anyway. No space for a 2nd drive.
Before systemd’s journal took over, older (oS) releases would use a syslog implementation; typically rsyslog. You can find out if you’re still using one by (i) checking to see if you have /var/log/messages (at least, anything recent appended to that) or (ii) seeing if such is even installed (i.e check with yast sm or whatever, whether rsyslog is installed).
There is no harm having multiple logging methods. (just duplication; in which case, if something gets spammy, then twice the amount of log spamming and decrease in available disk space …). No harm in removing. journald is fine on its own.
Check to see it you have any core dumps, rpm cache laying around… both will also be in /var:
/var/lib/systemd/coredump
/var/cache/zypp/packages/repoalias
/ … if you’re purposely retaining rpms - /var/cache/ZYPPER/RPMS … if you’ve manually installed an rpm (locally or remote)
Thanks. I already checked that /var/log/messages is not available. The total size of my /var/cache/zypp is 48M only. I deleted everything in /var/lib/systemd/coredump but there wasn’t much there too.