Hubfly spaceDocs
Console

Box · Guide

Box disks and data volumes

Choose what belongs on the root disk, attach persistent volumes, and grow capacity without losing track of the guest filesystem.

Root disk

Every Box has a root disk sized during creation. Managed images use a writable overlay above the selected base image.

  • The root disk can be enlarged; it cannot be shrunk. Choose enough space for OS packages, logs, and application files.
  • On supported managed Linux layouts the platform may grow the filesystem after block expansion. Check lsblk and df inside the guest before assuming the new space is usable.

Create and attach a data volume

Project data volumes are separate from the root disk. Create one with a name and size in GiB, then attach it to a Box.

  • The attach operation makes a block device available to the guest. Partition, format, mount, and add a stable mount rule inside Linux as needed.
  • Do not format an existing volume when reattaching it. Identify it by filesystem UUID or disk metadata rather than assuming a fixed /dev name.
  • A volume mutation can attach, detach, resize, or delete. Confirm the previous operation has completed before submitting a dependent change.

Resize and detach

Data volumes can grow, not shrink. The host enlarges the block device; the guest must expand its partition, LVM, and filesystem if those layers are present.

  • Back up data before filesystem work. Use the tool appropriate for your filesystem, such as resize2fs or xfs_growfs, after the block device reflects the new capacity.
  • Stop writes and unmount a volume before detaching it. A forceful detach while mounted can corrupt data.
  • A removed volume cannot be recovered through the Box API. Export or back up anything you need before deleting it.

Automating this workflow

See the matching Box API endpoints for exact request fields and response schemas. Host operations can continue after an API request returns.

Back to the Box guide · All Box API groups

Something unclear or out of date? Emailsupport@hubfly.spaceBack to top