Disk full and storage growth
Separate allocated disk capacity from guest partitions and filesystem usage.
Common symptoms
Disk full, No space left on device, inode full, read-only filesystem, partition, filesystem, disk resize, capacity unchanged
What to check
- Check guest filesystem space and inodes through SSH or Console, then identify the affected mount and files. Compare those readings with the disk capacity shown in server details.
- Preserve important data before changing files. Review known application logs, retention and caches; do not delete unknown system files or logs blindly to clear a disk full error.
- For more capacity, review the resize preview and limits. After disk growth completes, check whether the guest partition and filesystem also expanded; the required procedure depends on the operating system and layout.
Common questions
Why is Linux still full after increasing the server disk?
A larger virtual disk does not guarantee that the guest partition and filesystem have grown. Check all three sizes and the operating system's supported procedure before making partition changes.
Can No space left on device happen when free space remains?
Yes. Check inode use and the exact mount used by the application, as well as quotas or a read-only filesystem. Save important data before cleanup; deleting files can remove evidence or needed data.
Open the relevant page
Before contacting support
Include the server name, sanitized disk and inode usage, affected mount, error and resize result. Remove credentials and private filenames or data that are not needed for diagnosis.
Keep secrets out of support requests · Remove passwords, private keys, access tokens, TOTP codes, backup codes and full payment details from screenshots and logs. Share the server or order name, time with timezone and exact sanitized error.
This opens an editable ticket draft. Nothing is sent automatically.