Added a Data Volume but the System Disk Is Still Full? A VPS Checklist

Disclosure: UCELI provides cloud servers. This guide was prepared with AI assistance and checked against the linked documentation. It describes general storage questions, not a promise that a particular disk or migration feature is available.

Why can a server still report a full system disk after adding storage?

A cloud server can have a system disk for the operating system and one or more separate data volumes. Adding a volume may provide another filesystem rather than expanding the existing root filesystem. The exact behaviour depends on the provider and the server configuration. Before you buy or change storage, identify where the application actually writes its files.

1. Identify the full filesystem

On a Linux system that you are authorized to administer, df -h /path/to/application-data reports the filesystem containing that path. Replace the example with an existing, accessible path. Compare it with df -h / and the expected volume mount point. On systems using GNU df, df -i /path/to/application-data can also help check inode use; that is not necessarily the same as a provider's file-count quota. These commands report the currently visible filesystem; they do not prove that the expected device is mounted or identify every cause of a failure.

2. Check the new volume and application path

Confirm with your provider whether the additional storage is a separate device, how it is attached and mounted, and whether the mount persists after a restart. A new mount does not by itself move existing application data; mounting over a non-empty directory can temporarily hide its existing contents. If an application keeps writing to its original path, the original filesystem can still fill up. Do not assume the same storage behaviour across cloud platforms.

3. Plan any move before changing production

Document the application data location, permissions, service dependencies, available disk space and recovery steps. Take and verify a suitable backup before moving files or changing mounts. Plan for a maintenance window if the application needs to be stopped for a consistent copy. Test the procedure in an authorized environment; live databases and application state may need application-specific backup and restore procedures. A backup feature or migration service should not be assumed to be included.

4. Compare the full storage cost

Ask whether the listed capacity is the system disk, an additional volume, or both. Check the available disk types, attachment limits, backup and snapshot charges, billing period and what happens when the server is removed. Availability and terms can vary by location and configuration; confirm the actual order details.

UCELI lists cloud-server locations and reference configurations in its location catalog. For configuration questions, email support@uceli.com; do not send passwords or private keys.

References: DigitalOcean: why a separate volume does not increase its root disk; GNU Coreutils: df invocation; Red Hat: mounting file systems.

Comments

Post a Comment

Popular posts from this blog

Moving a website to a new server: an HTTPS and DNS checklist

Disclosure: UCELI provides cloud servers and domain services. This article was prepared with AI assistance and reviewed as general educational material. It does not describe a UCELI migration service or guarantee a particular outcome. A new server must answer for the right hostname, present a trusted certificate and serve the application correctly. Cached DNS can still direct visitors to the old server. This checklist is for teams with permission to test their own website and infrastructure. It focuses on a move where the public URL stays the same. Adapt it to your architecture and test in an authorized environment. A single check cannot guarantee zero downtime. 1. Record the current setup Before changing anything, document the hostnames and DNS records used by the website. Note the current A and AAAA records, their TTLs, whether a CDN or reverse proxy is in front, and where TLS terminates. Record the configuration and authorized operator. Also identify the application’s data dependenc...
Read more

Choosing a server for a self-hosted n8n workflow: five checks before deploying

Disclosure: UCELI provides cloud servers. This educational article was prepared with AI assistance and checked against the public sources linked below. It does not promise a managed n8n service, a one-click image, or a particular configuration, price or outcome. A self-hosted workflow can connect forms, databases and other services. It also puts a team in charge of the server, the workflow's credentials and the effects of each execution. Before ordering a cloud server for n8n, write down what the automation must do, what data it will handle and who will maintain it. The goal is not to pick a universal minimum server size. It is to compare an actual workload, deployment location and operating plan before committing to a configuration. 1. Describe the workflow and its busy periods List the events that start a workflow, the services it calls and the actions it performs. An automation that copies small form submissions to a test database has different needs from one that processes ...
Read more

Before choosing a Windows cloud server: five questions for a small team

Disclosure: UCELI provides cloud servers. This educational article was prepared with AI assistance and reviewed against the public sources linked below. It is not a licensing determination or a promise that any particular image, configuration or service is available. A small team may need Windows Server for an internal application, a scheduled job or software that its vendor supports only on Windows. Before comparing headline prices, write down what the application needs and how people will use it. A Windows image on a catalogue page is a starting point, not proof that your application, access model and licences are covered. 1. Which application and operating system versions work together? Ask the application vendor which Windows Server versions, architecture and components it supports. List database requirements, runtime dependencies, storage space, memory and any required drivers. Check both the application vendor’s support policy and the operating system lifecycle; an older versi...
Read more