Disk shows 6.4% used but every restart fails with "No space left on device" (ENOSPC)

My bot keeps crash looping with , even on completely trivial operations — including a plain for an empty folder, and on a restart where had nothing new to install (everything already satisfied, zero bytes written). My panel's disk usage graph shows only 6.4% used (65.2 MB / 1024 MB) — 958 MB reported as free — which doesn't match what's actually happening on the container. What I've already tried (no lasting effect): Deleted and via the File Manager to free space — this temporarily allowed a full to succeed on one restart, but the very next restart failed again on the exact same trivial call, with no new data written. Removed unnecessary dev dependencies ( , ) from that were being re downloaded on every restart. Confirmed via / output that the ENOSPC error is real (not an app bug) — standard tools like and themselves fail to write. Example crash (most recent, nothing new being installed): Requirement already satisfied: discord.py in ./.local/lib/python3.11/site packages... [... all packages "already satisfied", zero downloads ...] Traceback (most recent call last): File "/home/container/main.py", line 47, in <module asyncio.run(main()) ... File "/home/container/core/logger.py", line 81, in init Path(log dir).mkdir(parents=True, exist ok=True) File "/usr/local/lib/python3.11/pathlib.py", line 1116, in mkdir os.mkdir(self, mode) OSError: [Errno 28] No space left on device: 'logs' Earlier crash, also failing mid and mid : remote: Compressing objects: 100% (270/270), done. fatal: write error: No space left on device fatal: fetch pack: invalid index pack output ... Installing collected packages: pygments, pluggy, iniconfig, pytest, pytest asyncio ERROR: Could not install packages due to an OSError: [Errno 28] No space left on device: '.local/lib/python3.11/site packages/pygments' Could you check the actual disk usage/quota on the container's node? There seems to be a mismatch between what the dashboard reports and the real state of the filesystem — possibly a separate/smaller volume being hit, an inode limit, or a node level disk issue rather than my own storage quota. Server is currently stuck offline (auto restart disabled after repeated crashes within 60s). Would appreciate a look at the underlying host.