Troubleshooting and resolving disk space limitations on Vultr Compute instances to restore normal server functionality.
When the disk space on a Vultr Compute instance becomes full, it can interfere with normal server functionality. Common issues include database write failures, inability to view application logs, problems with changing the instance plan, and degraded instance performance. Clearing space on the instance's hard disk allows it to function normally again.
To free up disk space, you need to access your instance via SSH. However, in some cases, SSH access may fail due to the disk being completely full leaving no space even to initiate a session. If this happens, follow these steps:
Mount the SystemRescue OS on your instance through the Vultr Console and boot into it.
Mount the root block storage.
Use the chroot utility to access the root volume of your instance.
From within the chroot environment, check the disk space usage.
Output:
This command lists the top-level directories inside /var and how much space each is using. The -h flag shows the output in a human-readable format (e.g., K, M, G), and --max-depth=1 limits the listing to just the top-level folders. You can change the path or increase the depth to assess other parts of the file system.
After identifying which directories are using the most space, use the ls command with the -larSh flags to list individual files by size.
This command lists all files in the /var/log/ directory, sorted by size in descending order.
Rapid disk usage growth is often due to log files or application data piling up under /var. This directory frequently contains system logs, web server files, and databases, making it one of the most common sources of disk space issues.
After you identify large files or directories, remove them with the following commands:
To delete a file:
To delete an empty directory:
Be careful when deleting files. Avoid removing essential system files that may impact the instance's functionality.
After deleting old logs, unwanted software, unnecessary packages, or rotated log files, verify the available disk space using the df command:
Output:
This output shows each mounted file system’s total size, used space, available space, and usage percentage. The /dev/vda2 device typically represents your instance's main disk.
In some cases, due to organizational compliance or audit requirements, you may not be allowed to delete any log files or application data for example, if logs must be retained for up to 180 days.
In such scenarios, you can attach a Block Storage volume to your instance and move non-critical data or large log files to the new volume. This approach helps you free up space on your primary disk without violating data retention policies.
Always stop any services writing to the data (e.g., MySQL, Apache) before moving the files, and ensure correct permissions are preserved on the mounted volume.
0 Comments
Be the first to comment and share your perspective with the community.