@schmakus sagte in Festplatte voll ? Wie Speicher freigeben ?:
--- /var/log/journal -----------------------------------------------------------
/..
3,0 GiB [##########] /d42f7fb7c0134c239a49631175eaef44
Moin,
zu den anderen Verzeichnissen hast Du ja schon das nötige Rüstzeug bekommen.
Fürs journal, da kannst Du noch folgendes machen, damit dampfst Du das Journal auf eine Stunde ein.
sudo journalctl --flush --rotate --vacuum-time=1h
Aufschlüsslung der einzelnen Argumente:
--flush
Asks the journal daemon to flush any log data stored in /run/log/journal/ into /var/log/journal/, if persistent storage is enabled. This call does not return until the operation is complete. Note that this call is idempotent: the data is only flushed from /run/log/journal/ into /var/log/journal/ once during system runtime (but see --relinquish-var below), and this command exits cleanly without executing any operation if this has already happened. This command effectively guarantees that all data is flushed to /var/log/journal/ at the time it returns.
--rotate
Asks the journal daemon to rotate journal files. This call does not return until the rotation operation is complete. Journal file rotation has the effect that all currently active journal files are marked as archived and renamed, so that they are never written to in future. New (empty) journal files are then created in their place. This operation may be combined with --vacuum-size=, --vacuum-time= and --vacuum-file= into a single command, see above.
--vacuum-size=, --vacuum-time=, --vacuum-files=
Removes the oldest archived journal files until the disk space they use falls below the specified size (specified with the usual "K", "M", "G" and "T" suffixes), or all archived journal files contain no data older than the specified timespan (specified with the usual "s", "m", "h", "days", "months", "weeks" and "years" suffixes), or no more than the specified number of separate journal files remain. Note that running --vacuum-size= has only an indirect effect on the output shown by --disk-usage, as the latter includes active journal files, while the vacuuming operation only operates on archived journal files. Similarly, --vacuum-files= might not actually reduce the number of journal files to below the specified number, as it will not remove active journal files.
VG
Bernd
P.S.: Dann wurde Dir ja schon von @Thomas-Braun, die berechtigte Frage gestellt, was hat der ganze Desktopkram auf einem Server zu suchen, das war auch meine Frage, was Du da für eine Distribution in die VM installiert hast?
57,3 MiB [##########] firefox-esr_102.9.0esr-1~deb11u1_amd64.deb
53,4 MiB [######### ] firefox-esr_78.15.0esr-1~deb10u1_amd64.deb
35,1 MiB [###### ] libreoffice-common_1%3a6.1.5-3+deb10u7_all.deb
31,1 MiB [##### ] libreoffice-core_1%3a6.1.5-3+deb10u7_amd64.deb
15,3 MiB [## ] libwebkit2gtk-4.0-37_2.38.5-1~deb11u1_amd64.deb
13,4 MiB [## ] libwebkit2gtk-4.0-37_2.34.1-1~deb10u1_amd64.deb
8,2 MiB [# ] libreoffice-writer_1%3a6.1.5-3+deb10u7_amd64.deb
7,0 MiB [# ] libreoffice-calc_1%3a6.1.5-3+deb10u7_amd64.deb
7,0 MiB [# ] evolution-common_3.38.3-1+deb11u1_all.deb