This might be the simplest way to illustrate what I would like to achieve.
I have this:
It has a 70G partition for / and I am getting lots of disk full errors (mostly /tmp)
/tmp is not stored on disk (unless you changed the default configuration) but on a tmpfs which is stored in memory. If you are regularly running out of place in /tmp you are doing something wrong. You should probably look into storing your temporary files in your /home or /var/tmp (or configure whatever application is saving a lot of data to /tmp to store it elsewhere).
That might be quite hard without reinstalling unfortunately (depending on how much free space do you have in your /home currently). What filesystem do you use? If it’s ext4 which supports shrinking, then adding more space to your / will be trivial, but if you are using xfs, which doesn’t support shrinking, you might need to reinstall.
But they are already in one partition. nvme01n1p3 is the partition and this is the PV for the volume group.
How much space is still available in the home LV ? df -Th
Maybe you could shrink rl_wintermute-home by X amount of GB ( if the filesystem is ext4 ) and extend rl_wintermute-root. Easiest would be to remove swap or shrink swap and extend rl_wintermute-root.
LVM makes much more sense if you keep free extends available.. These extends can be assigned to a LV anytime when required.
Ugh… I am hopeless with filesystems, I think. Every time I think I understand something, I find out that something else is keeping me from understanding what I thought I knew.
worse is the fact that 500GB are still free. Now imagine this LV with an initial size of 1.5TB leaving 300GB as a reserve of free extends waiting to be assigned to any LV in the VG with one command!
you can’t shrink xfs only via xfsdump and xfsrestore.