When you grow the size of the Persistent Disk (GCE's analog of AWS's EBS, if the VM is running, it will automatically resize the partition and the file system for you. On Google Compute Engine, this is actually done automatically for you. You need to use a partition tool, such as fdisk, or parted, to change the size of the partition for you. Since the file system is on /dev/xvda1, that's why resize2fs is saying "nothing to do". You need to first resize the partition, and then you can resize the file system to the size of its block device. dev/xvda is 5.9T, but /dev/xvda1 is only 2T. The problem you're having is shown by the output of lsblk: sudo lsblk Tmpfs 97G 0 97G 0% anyone have any experience with this issue? The filesystem is already 536870655 (4k) blocks long. dev/xvda1: LABEL="cloudimg-rootfs" UUID="*****" TYPE="ext4" sudo lsblk sudo df -hįilesystem Size Used Avail Use% Mounted on Using lsblk I can correctly see the total disk space of 5.9T. On the instance I used resize2fs to resize the partition and it does not work (even after rebooting). I have updated the AWS volume to 6TB without difficulties. It has a 2TB ext4 partition which I am trying to resize to 6TB. I have an AWS EC2 instance running on Ubuntu 16.04.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |