Creating and resizing Compute volumes

​

How to create a disk

nebius compute disk create \
  --name <disk_name> \
  --source-image-family-image-family <OS_image> \
  --type network_<ssd|ssd_non_replicated|ssd_io_m3> \
  --disk-encryption-type disk_encryption_managed \
  --size-gibibytes <size> \
  --block-size-bytes <block_size>

​

How to create a shared filesystem

nebius compute filesystem create \
  --name <filesystem_name> \
  --type network_ssd \
  --size-gibibytes <size> \
  --block-size-bytes <block_size>

​

Volume parameters

​

Metadata

​

Type, encryption and size

• Type (type): The volume type. See available types of disks and shared filesystems. Required at creation, and cannot be changed later.
• Enable data encryption (disk-encryption-type): Whether a volume should support data encryption. Encryption allows you to store personal and other sensitive data securely on volumes, and reduce the risk of unauthorized access. Use this parameter only for secondary disks of the Network SSD Non-replicated and Network SSD IO M3 types. Filesystems and Network SSD disks support encryption by default, and you cannot disable it. For more information, see Encryption of disks. In the CLI, use --disk-encryption-type disk_encryption_managed to enable encryption.
• Size (size-gibibytes, size-mebibytes, size-kibibytes or size-bytes): The volume size. See requirements for sizes of disks and shared filesystems in their comparison tables. Required at creation. After creation, size can only be increased. When using the CLI, you can set the volume size in GiB, MiB, KiB or B using a respective parameter. Maximum size of a boot disk is 30,720 GiB (30 TiB).
• Block size (block-size-bytes): The data block size for the volume. The data stored on the volume is divided into blocks of this size on the underlying physical drives. Cannot be changed after the volume is created.
  Currently, the block size cannot be set when creating a volume in the web console.
  The block size must be a power of two between 4096 bytes (4 KiB) and 131,072 bytes (128 KiB). The default value is 4096 bytes (4 KiB). For maximum IOPS, reads and writes to a volume should be close to its block size.

​

Boot disk image

• Boot image (source-image-family-image-family): An image provided by Nebius AI Cloud to use for a boot disk. For details, see Boot disk images for Compute virtual machines.

​

How to resize a volume

1. Change the volume size:
   • Web console
   • CLI

   1. In the sidebar, go to  Storage → Disks or  Storage → Shared filesystems. Alternatively, go to the virtual machine where the volume is attached and find it in the Disks or Shared filesystems tab.
   2. Click the volume you want to resize and go to the Settings tab.
   3. In the Parameters section, enter the new Size value or use the slider to set the new size.
   4. Click Save changes.

   1. If you haven’t saved the disk or filesystem’s ID when creating it, get its ID:
      export DISK_ID=$(nebius compute disk get-by-name \
        --parent-id <project_ID> \
        --name <disk_name> \
        --format json | jq -r ".metadata.id")
      
      For a filesystem, use nebius compute filesystem get-by-name with the same parameters.
   2. Run nebius compute disk update for a disk, or nebius compute filesystem update for a shared filesystem, and set the new size by using one of the --size-gibibytes, --size-mebibytes, --size-kibibytes or --size-bytes parameters. Here is an example for a disk:
      nebius compute disk update \
        --id $DISK_ID \
        --size-gibibytes <size>
      
2. If you resized a secondary disk and it is currently attached to a running virtual machine, do the following:
   1. Restart this VM.
   2. Connect to this VM.
   3. Install the cloud-guest-utils package that manages the disk partitions:
      sudo apt-get update && sudo apt-get install -y cloud-guest-utils
      
   4. List disks and partitions:
      lsblk --paths
      
      Output example:
      NAME          MAJ:MIN  RM   SIZE  RO  TYPE  MOUNTPOINTS
      /dev/vda      253:0     0    10G   0  disk
      ├─/dev/vda1   253:1     0     9G   0  part  /
      ├─/dev/vda14  253:14    0     4M   0  part
      ├─/dev/vda15  253:15    0   106M   0  part  /boot/efi
      └─/dev/vda16  259:0     0   913M   0  part  /boot
      /dev/vdb      253:16    0     1M   0  disk
      /dev/vdc      253:32    0    20G   0  disk
      └─/dev/vdc1   253:33    0    10G   0  part  /mnt/disk-0
      
      Find the device name of the resized disk and get the name of its last partition. The secondary disk is most likely the last one in the list. Also, check the SIZE column: it shows that the disk size is increased, but the partition size stays the same. In this example, the required device name is /dev/vdc, and the partition is /dev/vdc1.
   5. Grow the partition to fill the disk:
      sudo growpart /dev/vdc 1
      
      If you work with a disk that has a device name other than /dev/vdc, change the device name and the partition index 1 in the current command and commands below. You can get the index of the partition from its name. Only the last partition may be grown.
      In the commands, you can use the device ID of the disk (/dev/disk/by-id/virtio-disk-0) instead of the device name (/dev/vdc). Run the ls /dev/disk/by-id command to get device IDs for all disks.
   6. Refresh the kernel partition table for the disk and wait for the device information to be updated:
      sudo partprobe /dev/vdc && sudo udevadm settle
      
   7. Show information about partitions and check that the size of the partition has increased:
      lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINT /dev/vdc
      
      Output example:
      NAME    SIZE  TYPE  FSTYPE  MOUNTPOINT
      vdc      25G  disk
      └─vdc1   25G  part  ext4    /mnt/disk-0
      
   8. Grow the ext4 filesystem on the increased partition:
      sudo resize2fs /dev/vdc1
      
   9. Check that the filesystem size has increased:
      df -hT
      
      Output example:
      Filesystem      Type       Size   Used  Avail  Use%  Mounted on
      tmpfs           tmpfs      795M   1.1M   794M    1%  /run
      /dev/vda1       ext4        38G   3.3G    35G    9%  /
      tmpfs           tmpfs      3.9G      0   3.9G    0%  /dev/shm
      tmpfs           tmpfs      5.0M      0   5.0M    0%  /run/lock
      cloud-metadata  virtiofs   252G    16K   252G    1%  /mnt/cloud-metadata
      /dev/vdc1       ext4        25G    24K    24G    1%  /mnt/disk-0
      /dev/vda16      ext4       881M   174M   645M   22%  /boot
      /dev/vda15      vfat       105M   6.2M    99M    6%  /boot/efi
      tmpfs           tmpfs      795M    12K   795M    1%  /run/user/1001
      

​

See also

• Types of storage volumes in Compute
• Attaching and mounting Compute volumes to VMs