This is somehow « annoying » :
if there was enough free space before and journal files were created, and subsequently something else causes the file system to fill up, journald will stop using more space, but it will not be removing existing files to reduce the footprint again, either.
…and explain how it can grow big.
As usual, thanks for the links. I’ll do a bit of vacuum and maybe set some limits.
Doing so ( removing unused snaps and debs, moving /var/log to another disk ), I went from
django@ASGARD:~$ df -Th | grep -v loop*
Sys. de fichiers Type Taille Utilisé Dispo Uti% Monté sur
(…)
/dev/sda1 ext4 24G 21G 2,0G 92% /
(…)
django@ASGARD:~$
to
/dev/sda1 ext4 24G 17G 5,4G 76% /