> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/system-administration/common-issues/disk-filled-up-to-100.md). # Disk filled up to 100% How to deal with a server that had its disk filled fully up ### 1. Enter your servers console You can find instructions for this in the following articles: * For VPS: [Entering the VNC console](/virtualization-platform/server-management/entering-the-vnc-console.md) * For dedicated servers: [Entering console](/dedicated-servers/server-management/entering-console.md) ### 2. Log into your VPS Then using your credentials that you have either set yourself within the server, or set at the reinstallation stage, log into your server. ### 3. Wipe the journal logs of your server The most common cause of a disk being filled up is too many logs being generated. You can wipe them with the following commands: ``` journalctl --rotate journalctl --vacuum-time=1s ``` Afterward, change the vacuum time setting to 2 days via the following command: ``` journalctl --vacuum-time=2d ``` ### 4. SSH into your server, and delete some files Now, your server should regain its connectivity, and you should be able to SSH into your server once again. Ncdu is a very useful tool in here. It will automatically scan all directories, and show you where the biggest files reside. You can install, and use it with the following commands: ``` sudo apt install ncdu cd / ncdu ``` We recommend that you do not use your disk above \~90%. This will always leave some head room for new logs, and files generated by your applications. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://legacy.docs.synteq.com/system-administration/common-issues/disk-filled-up-to-100.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.