The following example shows the volumes on a Nitro-based instance:
[system-user ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 30G 0 disk ├─sda1 8:1 0 9.9G 0 part / ├─sda14 8:14 0 4M 0 part └─sda15 8:15 0 106M 0 part /boot/efi
- The root volume,
/dev/sda, has a partition,
/dev/sda1. While the size of the root volume reflects the new size, 30 GB, the size of the partition reflects the original size, 30 GB, and must be extended before you can extend the file system.
To extend the partition on the root volume, use the following growpart command. Notice that there is a space between the device name and the partition number.
[system-user ~]$ sudo growpart /dev/sda 1
You can verify that the partition reflects the increased volume size by using the lsblk command again.
[system-user ~]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 30G 0 disk ├─sda1 8:1 0 29.9G 0 part / ├─sda14 8:14 0 4M 0 part └─sda15 8:15 0 106M 0 part /boot/efi
Extending the File System
Use a file system-specific command to resize each file system to the new volume capacity. For a file system other than the examples shown here, refer to the documentation for the file system for instructions.
Example: Extend an ext2, ext3, or ext4 file system
Use the df -h command to verify the size of the file system for each volume. In this example,
/dev/sda1 reflects the original size of the volume, 10 GB.
[system-user ~]$ df -h /dev/root 9.6G 3.9G 5.7G 41% / ...
Use the resize2fs command to extend the file system on each volume.
[system-user ~]$ sudo resize2fs /dev/sda1
You can verify that each file system reflects the increased volume size by using the df -h command again.
[system-user ~]$ df -h /dev/root 29G 3.8G 26G 14% / ...