You are not logged in.
When trying to resize the logical volumes, I have conflicting information. I'm trying to adjust the size of the lv_root logical volume and add more space. While this shows as correct in lsblk as seen below, doing df -h yields different results. What do I do so that way I can access the newly allocated storage for /volgroup0/lv_root for install new software?
This is with lsblk
loop0 7:0 0 4K 1 loop /var/lib/snapd/snap/bare/5
loop1 7:1 0 74.1M 1 loop /var/lib/snapd/snap/core22/1033
loop2 7:2 0 497M 1 loop /var/lib/snapd/snap/gnome-42-2204/141
loop3 7:3 0 74.2M 1 loop /var/lib/snapd/snap/core22/1122
loop4 7:4 0 91.7M 1 loop /var/lib/snapd/snap/gtk-common-themes/1535
loop5 7:5 0 70.9M 1 loop /var/lib/snapd/snap/runelite/26
loop6 7:6 0 70.9M 1 loop /var/lib/snapd/snap/runelite/27
loop7 7:7 0 39.1M 1 loop /var/lib/snapd/snap/snapd/21184
loop8 7:8 0 38.7M 1 loop /var/lib/snapd/snap/snapd/21465
nvme0n1 259:0 0 476.9G 0 disk
├─nvme0n1p1 259:1 0 512M 0 part
├─nvme0n1p2 259:2 0 512M 0 part /boot
└─nvme0n1p3 259:3 0 475.9G 0 part
└─volgroup0 254:0 0 475.9G 0 crypt
├─volgroup0-lv_root 254:1 0 70G 0 lvm /
└─volgroup0-lv_home 254:2 0 405.9G 0 lvm /homeThis is with df -h
dev 16G 0 16G 0% /dev
run 16G 1.8M 16G 1% /run
efivarfs 192K 48K 140K 26% /sys/firmware/efi/efivars
/dev/mapper/volgroup0-lv_root 30G 28G 603M 98% /
tmpfs 16G 0 16G 0% /dev/shm
tmpfs 16G 8.0K 16G 1% /tmp
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-udev-load-credentials.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-sysctl.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup-dev.service
/dev/mapper/volgroup0-lv_home 30G 27G 1.1G 97% /home
/dev/loop0 128K 128K 0 100% /var/lib/snapd/snap/bare/5
/dev/loop6 71M 71M 0 100% /var/lib/snapd/snap/runelite/27
/dev/loop7 40M 40M 0 100% /var/lib/snapd/snap/snapd/21184
/dev/loop8 39M 39M 0 100% /var/lib/snapd/snap/snapd/21465
/dev/loop3 75M 75M 0 100% /var/lib/snapd/snap/core22/1122
/dev/loop1 75M 75M 0 100% /var/lib/snapd/snap/core22/1033
/dev/loop2 497M 497M 0 100% /var/lib/snapd/snap/gnome-42-2204/141
/dev/loop5 71M 71M 0 100% /var/lib/snapd/snap/runelite/26
/dev/loop4 92M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/nvme0n1p2 488M 160M 292M 36% /boot
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-vconsole-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-tmpfiles-setup.service
tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service
tmpfs 3.2G 28K 3.2G 1% /run/user/1000Offline
pacman's check on whether a package can be installed is done by blocks, so check the number of available blocks reported by the file system (e.g. stat -f).
Offline
Seems like you (perhaps excessively) grow your LV but forgot to grow the filesystem along with it (resize2fs in case of ext4, different filesystems have different utilities for this). So the filesystems are still the old small size.
Note that if you assign 100% of your VG space, you won't be able to grow again or create other LV or snapshots in the future... and shrinking is much harder than growing (impossible for some filesystems).
So instead of going to 100% in one step, it might make sense to only grow as required (by +10G at a time) as it gives you more options with LVM.
Also remember to clear out your pacman caches and rotate logs to free up space on /.
Offline