Unable to resize AWS EC2 storage with growpart

I tried doing that before, and just gave it another try. What I get is this:

sudo pvresize /dev/nvme0n1p6
  Physical volume "/dev/nvme0n1p6" changed
  1 physical volume(s) resized / 0 physical volume(s) not resized

But when I go in and check with vgs I still get the same size displayed:

sudo vgs
  VG #PV #LV #SN Attr   VSize   VFree
  vg   1   3   0 wz--n- 110.83g 8.00m

As @Paul Frederiksen has already asked, what flavour of Linux is this? I'm not familiar with an AMI that puts root, swap & tmp on a partition of the system disk under LVM control. It would be nice to be able to spin up an EC2 with it to test a few things.

Back to your question, the doc I linked to deals with growing an EBS volume where it's the secondary disk, which is a bit different to what you're trying to do here.

So when you run lsblk, then increase the EBS & run growpart, after this lsblk shows the same as before? I think that growing the partition when it's the running root disk isn't enough, you actually have to delete and re-add the partition with the updated disk geometry (this sounds familiar from when I've worked on Linux VMs in the past).

This looks close to what you are trying to achieve https://serverfault.com/questions/861517/centos-7-extend-partition-with-unallocated-space

This is running Ubuntu 18.04.6 LTS (GNU/Linux 4.15.0-191-generic x86_64). I'll take a look through that serverfault question as well.

Also, as for this: "So when you run lsblk, then increase the EBS & run growpart, after this lsblk shows the same as before?"

Running lsblk and before changing the EBS size in the AWS console was showing 112GB. I updated that to 224GB in the AWS console and ran lsblk again and it showed the new 224GB size for the main nvme0n1 drive, and keeps the old size for the partition nvme0n1p6. Then I run the growpart command, and it tells me that it's resizing it, doubling it, but then when I use lsblk it still shows the old size.

I ran that command, and this is what I got:

 sudo lvextend -r -l +100%FREE /dev/mapper/vg-root

  Size of logical volume vg/root changed from 94.61 GiB (24221 extents) to 94.62 GiB (24223 extents).
  Logical volume vg/root successfully resized.
resize2fs 1.44.1 (24-Mar-2018)
Filesystem at /dev/mapper/vg-root is mounted on /; on-line resizing required
old_desc_blocks = 12, new_desc_blocks = 12
The filesystem on /dev/mapper/vg-root is now 24804352 (4k) blocks long.

I'm not sure why it only extended by .01GB... When I run lsblk it looks like I should have the full 224GB available, and it doesn't look like it's being used:

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
nvme0n1     259:0    0   224G  0 disk
|-nvme0n1p1 259:1    0     1M  0 part
|-nvme0n1p2 259:2    0     1K  0 part
|-nvme0n1p5 259:3    0   976M  0 part /boot
`-nvme0n1p6 259:4    0 110.9G  0 part
  |-vg-root 253:0    0  94.6G  0 lvm  /
  |-vg-tmp  253:1    0   976M  0 lvm  /tmp
  `-vg-swap 253:2    0  15.3G  0 lvm  [SWAP]

I think before that I have to resize the partition right? Which is what growpart is supposed to do, but doesn't seem to be working.