When I execute pvmove it says not enough extents.
Well, there aren't any, and free space in filesystems doesn't count.
/dev/mapper/vg0-personal 10793808 3037966 7293737 30% /personal
This is a filesystem
10793808 blocks large,
3037966 blocks used,
30% used. So there is free space but that's filesystem free space, not LVM free space.
The filesystem is still
10793808 blocks large, and that'll be how large the
/dev/mapper/vg0-personal LV is and how much space that LV occupies in the LVM at minimum (unless you're using specialties like thin provisioning).
You seem to have several more of such LVs and as a result your VG is pretty much full:
PV VG Fmt Attr PSize PFree Used
/dev/sdc1 vg0 lvm2 a-- <3.64t 3.29g <3.64t
/dev/sdf1 vg0 lvm2 a-- <465.76g 0 <465.76g
/dev/sdf1 is ~465G (PSize) and the only PV with non-0 free space is
/dev/sdc1 with only ~3G (PFree). As such there is next to no free space in that VG. In order to remove
/dev/sdf1, you'll have to free up another ~462G somehow.
If you have free space inside your filesystems, that's great, but LVM does not care about that. LVM cares about the size of the logical volumes / block devices it manages, not whatever you decided to store on top of those block devices.
So in order to proceed, you'll have to shrink filesystems, or remove filesystems altogether, or switch to thin provisioning (risky in many ways), or decide to leave things as is after all and not remove a drive.
In any case, make sure to have good backups of your data.