Devpilot
Servers

Storage and Volumes

View disk usage across mount points and manage cloud volumes on supported providers.

Storage and Volumes

The Storage tab shows two things: the live disk usage Devpilot has collected from the server, and — for servers running on supported cloud providers — the cloud volumes attached to your account.

Disk Usage

Devpilot's monitoring agent reports per-mount-point storage metrics. The Storage tab summarizes:

  • Filesystem and mount point — For example /dev/sda1 mounted at /.
  • Total, used, and available space for each mount point.
  • Usage percentage per mount point.

Any mount point over 85% full deserves attention. Above 95%, expect application errors, failed writes, and logging to stop. Root partitions at 100% can destabilize the entire server.

Use this view to identify which disk is filling up before digging in with the File Manager or Web Terminal.

Cloud Volumes (Managed via Provider API)

If the server was provisioned through Devpilot on a supported cloud provider with valid credentials, Devpilot can manage cloud-side volumes through the provider's API. This lets you attach extra block storage without leaving the dashboard.

Before the volume section works, Devpilot checks capabilities for the server. If the server isn't on a supported provider, or cloud credentials aren't configured, the volume actions are hidden with an explanatory message.

Supported Providers

Managed cloud volumes are currently available on:

ProviderCreateAttachDetachResizeDelete
DigitalOceanYesYesYesYesYes
HetznerYesYesYesYesYes
VultrYesYesYesYesYes
AWS (EBS)YesYesYesYesYes
AzureYesYesYesYesYes
Google CloudYesYesYesYesYes

Servers connected via SSH only (no linked cloud credentials) can still use Devpilot's disk usage view and manual mount/unmount/format/fstab tools over SSH — the cloud-side actions above simply won't appear.

Creating a volume

Open the Volumes section

On the Storage tab, open the Volumes panel and click Create Volume.

Configure the volume

Provide:

  • Name — A label using letters, numbers, hyphens, and underscores.
  • Size (GB) — Any whole number from 1 up to 16,384 GB.
  • Filesystem (optional)ext4 or xfs. You can also format the volume after creation.

The volume is created in the server's region on the same cloud provider account, which is required for attachment.

Confirm

Click Create. Devpilot calls the cloud provider's API to create the volume. This usually takes seconds to a minute.

Attaching a volume

Open a volume and click Attach, then select the target server in the same region. Devpilot attaches the volume as a block device on the server (for example /dev/sdb). You still need to mount it before applications can read or write files.

Formatting a volume

If you didn't format at creation, open the volume and click Format, then choose ext4 or xfs.

Formatting erases every byte currently on the volume. Only format new volumes or volumes you're intentionally wiping.

Mounting and unmounting

Mount a volume to a directory on the server (for example /mnt/data) to make it usable by applications. Unmount before detaching or destroying.

Make sure no processes are actively reading or writing the mount point before unmounting. Active handles can cause the unmount to fail or data to be lost.

Resizing

Increase a volume's size from the volume detail view. Volume shrinking is not supported — cloud providers generally don't allow it without manual data migration. When the volume is attached and mounted, Devpilot also expands the filesystem so the extra space is usable.

Detaching and deleting

  • Detach — Disconnect the volume from the server. Unmount first to avoid data corruption.
  • Delete — Permanently destroy the volume on the cloud provider side. This is irreversible; back up any data you still need.

Never detach a mounted volume while applications are using it. Unmount first, then detach.

Filesystem Actions (SSH)

Beyond the cloud-provider API, Devpilot also exposes a few filesystem tools that run over SSH. These work on any server — including ones connected to Devpilot without cloud credentials — and let you finish the job after a new block device is attached.

Format a device

Choose Format on an attached but unused device and pick ext4, xfs, or btrfs. Devpilot runs the matching mkfs command over SSH.

Formatting destroys every byte on the device. Double-check the device path (for example, /dev/sdb, not /dev/sda) before confirming.

Mount a device

Give Devpilot a device (/dev/sdb1), a mount point (/mnt/data), and a filesystem type (ext4, xfs, or btrfs). Devpilot creates the mount point if needed and mounts the device.

Protected system paths — /, /boot, /boot/efi, /home, /var, /tmp, /usr, and /etc — are blocked as mount targets to prevent you from hiding the running system behind a fresh volume.

Unmount a device

Give Devpilot the mount point and it runs umount for you. Close open file handles on the mount point first or the command will fail.

Manage /etc/fstab

To make a mount persist across reboots, add an /etc/fstab entry. Devpilot needs:

  • Device — A path or UUID that identifies the volume across reboots.
  • Mount point — Where it should mount.
  • Filesystem typeext4, xfs, or btrfs.
  • Options (optional) — Mount options like defaults,noatime.
  • dump and pass (optional) — Standard fstab fields, both default to 0.

Remove the entry from the same view when you no longer need it.

A bad /etc/fstab entry can stop the server from booting. Test the mount manually (with Mount a device) before adding it to fstab, and be cautious with mount options you don't recognize.

What Storage You Don't Manage Here

  • Disk I/O / IOPS dashboards — Devpilot collects high-level throughput and utilization metrics, not fine-grained IOPS charts. Use your cloud provider's monitoring for block-storage IOPS if you need that depth.
  • RAID, LVM, and local partitioning — Manage these directly on the server via the Terminal or Scripts.

Next Steps