Requesting a sanity check when resizing filesystem after resizing pve-data LV

Dec 19, 2017
3
0
6
Hello,
I'm working on giving my PVE 4.4 hypervisor cluster larger disks for more VM space, and I am able to extend the volume group across the new disk, move the physical volumes to the new group, removed the old disk from the VG, and then extend the logical volume to the end of the new disk.
The issue is that every guide I'm reading about extending a logical volume requires that I do resize2fs or resize the lv with --resizefs flags or something. When I try resize2fs, I get
Bad magic number in super-block while trying to open /dev/pve/data
Couldn't find valid filesystem superblock.

When I try lvextend --extents +100%FREE --resizefs /dev/pve/data, it tells me that lvm-thin doesn't have a filesystem so it is ignoring that flag.

Is there something I am missing? I don't want to get halfway through this cluster only to find that I broke every machine I worked on.

Thank you.