OCI Sniper v5

Boot volumes

Click scan to load boot volumes.

Resize boot volume (custom size)

Grow an existing boot volume in place — no terminate/relaunch, no data loss. The new size must be larger than the current size (OCI cannot shrink). Custom sizes above 200 GB are allowed.

Boot volume

New size (GB)

Stop attached instance before resize (offline resize, safest)

Start instance after resize

Launch from existing boot volume

Select a detached volume above, then choose subnet and shape below to launch a new instance using that volume. Optionally grow the volume to a custom size first.

Target boot volume

New instance name

New size (GB) — custom adjustment

Leave empty to keep the current size. Must be larger than the current size.

Re-attach boot volume to instance

Attach the selected detached volume to an existing instance in the same availability domain. The instance is stopped if it is running, then the volume is attached. Optionally start it afterwards.

Target instance

Start instance after attach

ⓘ Resize tip

OCI boot volumes can be grown in place (increase only — shrinking is not supported). Use Resize volume above to expand a volume with its data intact; paravirtualized volumes support online growth, but stopping the instance first (offline resize) is the safest option.

After the resize, extend the partition inside the OS, e.g. Oracle Linux: sudo /usr/libexec/oci-growfs (Ubuntu: sudo apt-get install -y oci-utils && sudo /usr/libexec/oci-growfs), then verify with df -h /.
Always Free storage is capped at 200 GB per boot volume — sizes above 200 GB may incur charges.

🎯 OCI Sniper