Everyone:
I have a problem upgrading to Fedora 41. After I download all the packages and import the keys, it's telling me I need around 5 GB more space on the / filesystem. The / system is on a partition that has only 50 GiB total, and 395.2 MiB free. (I use the GiB and MiB symbols deliberately.) Specifically it says I need to find 4437 MB on that system. If I have to repartition, I understand that I might as well do a fresh install. My data is safe enough - it's on a completely different physical device, mounted as /crypt - and another petition on the "root device" is present with 47.4 GiB free (there's nothing on it but the contents of /home). But I can't remember half the stuff I installed from non-core repositories like rpmfusion, and if I have to install from scratch, I'll lose a lot of applications. (The kernels are on /boot, which is a 1.0 GiB partition that has more than 500 MiB free.) How can I free up that extra space (say, 5GiB for good measure) without having to reformat the root device for a fresh install?
Temlakos
If you can, show people actual command outputs, it'll make it easier to help.
Do you have any flex with LVM or are your filesystems directly on block devices? e.g.
root@fedora:~# pvs; vgs; lvs
Review your mounts/filesystems, e.g.:
root@fedora:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS zram0 252:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 1G 0 part /boot └─nvme0n1p3 259:3 0 952.3G 0 part /home / root@fedora:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p3 953G 136G 817G 15% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 84K 16G 1% /dev/shm efivarfs 246K 47K 195K 20% /sys/firmware/efi/efivars tmpfs 6.3G 2.3M 6.3G 1% /run /dev/nvme0n1p3 953G 136G 817G 15% /home /dev/nvme0n1p2 974M 292M 615M 33% /boot tmpfs 16G 672K 16G 1% /tmp /dev/nvme0n1p1 599M 20M 580M 4% /boot/efi tmpfs 3.2G 12M 3.1G 1% /run/user/1000
Understand where your space is being consumed on the / device. Don't use '-h' so you can sort easily, use 'x' so as to limit your 'du' to a single device. e.g.
root@fedora:~# du -xk / | sort -n -k1 | tail -20 1480504 /usr/lib/python3.12/site-packages/azure 1561480 /var/spool/abrt/ccpp-2024-04-27-13:17:11.106624-89698 1602284 /opt 2184720 /var/spool 2184720 /var/spool/abrt 2226356 /var/cache 2344592 /usr/lib/python3.12 2344592 /usr/lib/python3.12/site-packages 3429168 /usr/share 4395972 /usr/lib 5354284 /usr/lib64 9976580 /var/lib/flatpak/repo/objects 9980444 /var/lib/flatpak/repo 10041060 /var/lib/flatpak 14354904 /usr 33858716 /var/lib/libvirt/images 33858724 /var/lib/libvirt 44206592 /var/lib 49862812 /var 65976164 /
(Optional, `du -xk / | sort -n -k1 | tac` if you prefer your output the other way round...)
Next, is any of that stuff you don't need? So in my example, I could look at my libvirt images, or flatpacks (which I will, because I'm not specifically using any, to my knowledge.)
Do you have logs you can rotate/archive from /var (if /var's on your / drive rather than its own block device / partition.)
Do you have any Yum cache lying around from old major version upgrades?
What's on the filesystem that *isn't* owned by a package, should it be there?
On Sun, 10 Nov 2024 at 11:23, Terry Hurlbut temlakos@gmail.com wrote:
Everyone:
I have a problem upgrading to Fedora 41. After I download all the packages and import the keys, it's telling me I need around 5 GB more space on the / filesystem. The / system is on a partition that has only 50 GiB total, and 395.2 MiB free. (I use the GiB and MiB symbols deliberately.) Specifically it says I need to find 4437 MB on that system. If I have to repartition, I understand that I might as well do a fresh install. My data is safe enough - it's on a completely different physical device, mounted as /crypt - and another petition on the "root device" is present with 47.4 GiB free (there's nothing on it but the contents of /home). But I can't remember half the stuff I installed from non-core repositories like rpmfusion, and if I have to install from scratch, I'll lose a lot of applications. (The kernels are on /boot, which is a 1.0 GiB partition that has more than 500 MiB free.) How can I free up that extra space (say, 5GiB for good measure) without having to reformat the root device for a fresh install?
Temlakos
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Oh, and according to https://unix.stackexchange.com/questions/414963/fedora-25-to-27-upgrade-not-... you could also try symlinking or bind mounting /var/lib/dnf/system-upgrade over to a device with more free disk space. I imagine having the upgrade packages on the root device is probably a better option if you can, so exercise caution.
On Sun, 10 Nov 2024 at 11:58, Will McDonald wmcdonald@gmail.com wrote:
If you can, show people actual command outputs, it'll make it easier to help.
Do you have any flex with LVM or are your filesystems directly on block devices? e.g.
root@fedora:~# pvs; vgs; lvs
Review your mounts/filesystems, e.g.:
root@fedora:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS zram0 252:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 1G 0 part /boot └─nvme0n1p3 259:3 0 952.3G 0 part /home / root@fedora:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p3 953G 136G 817G 15% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 84K 16G 1% /dev/shm efivarfs 246K 47K 195K 20% /sys/firmware/efi/efivars tmpfs 6.3G 2.3M 6.3G 1% /run /dev/nvme0n1p3 953G 136G 817G 15% /home /dev/nvme0n1p2 974M 292M 615M 33% /boot tmpfs 16G 672K 16G 1% /tmp /dev/nvme0n1p1 599M 20M 580M 4% /boot/efi tmpfs 3.2G 12M 3.1G 1% /run/user/1000
Understand where your space is being consumed on the / device. Don't use '-h' so you can sort easily, use 'x' so as to limit your 'du' to a single device. e.g.
root@fedora:~# du -xk / | sort -n -k1 | tail -20 1480504 /usr/lib/python3.12/site-packages/azure 1561480 /var/spool/abrt/ccpp-2024-04-27-13:17:11.106624-89698 1602284 /opt 2184720 /var/spool 2184720 /var/spool/abrt 2226356 /var/cache 2344592 /usr/lib/python3.12 2344592 /usr/lib/python3.12/site-packages 3429168 /usr/share 4395972 /usr/lib 5354284 /usr/lib64 9976580 /var/lib/flatpak/repo/objects 9980444 /var/lib/flatpak/repo 10041060 /var/lib/flatpak 14354904 /usr 33858716 /var/lib/libvirt/images 33858724 /var/lib/libvirt 44206592 /var/lib 49862812 /var 65976164 /
(Optional, `du -xk / | sort -n -k1 | tac` if you prefer your output the other way round...)
Next, is any of that stuff you don't need? So in my example, I could look at my libvirt images, or flatpacks (which I will, because I'm not specifically using any, to my knowledge.)
Do you have logs you can rotate/archive from /var (if /var's on your / drive rather than its own block device / partition.)
Do you have any Yum cache lying around from old major version upgrades?
What's on the filesystem that *isn't* owned by a package, should it be there?
On Sun, 10 Nov 2024 at 11:23, Terry Hurlbut temlakos@gmail.com wrote:
Everyone:
I have a problem upgrading to Fedora 41. After I download all the packages and import the keys, it's telling me I need around 5 GB more space on the / filesystem. The / system is on a partition that has only 50 GiB total, and 395.2 MiB free. (I use the GiB and MiB symbols deliberately.) Specifically it says I need to find 4437 MB on that system. If I have to repartition, I understand that I might as well do a fresh install. My data is safe enough - it's on a completely different physical device, mounted as /crypt - and another petition on the "root device" is present with 47.4 GiB free (there's nothing on it but the contents of /home). But I can't remember half the stuff I installed from non-core repositories like rpmfusion, and if I have to install from scratch, I'll lose a lot of applications. (The kernels are on /boot, which is a 1.0 GiB partition that has more than 500 MiB free.) How can I free up that extra space (say, 5GiB for good measure) without having to reformat the root device for a fresh install?
Temlakos
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Answers to Will's questions:
The message, which was the output of dnf system-upgrade download --releasever=41 --allowerasing, ended with:
Error summary:
Disk Requirements:
At least 4437 MB more space required on the / filesystem.
Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 4K 1 loop /var/lib/snapd/snap/bare/5 loop1 7:1 0 55.7M 1 loop /var/lib/snapd/snap/core18/2829 loop2 7:2 0 55.4M 1 loop /var/lib/snapd/snap/core18/2846 loop3 7:3 0 74.2M 1 loop /var/lib/snapd/snap/core22/1621 loop4 7:4 0 73.9M 1 loop /var/lib/snapd/snap/core22/1663 loop5 7:5 0 66.2M 1 loop /var/lib/snapd/snap/core24/490 loop6 7:6 0 66.2M 1 loop /var/lib/snapd/snap/core24/609 loop7 7:7 0 164.8M 1 loop /var/lib/snapd/snap/gnome-3-28-1804/194 loop8 7:8 0 164.8M 1 loop /var/lib/snapd/snap/gnome-3-28-1804/198 loop9 7:9 0 504.2M 1 loop /var/lib/snapd/snap/gnome-42-2204/172 loop10 7:10 0 505.1M 1 loop /var/lib/snapd/snap/gnome-42-2204/176 loop11 7:11 0 402.4M 1 loop /var/lib/snapd/snap/gnome-46-2404/42 loop12 7:12 0 406.3M 1 loop /var/lib/snapd/snap/gnome-46-2404/48 loop13 7:13 0 91.7M 1 loop /var/lib/snapd/snap/gtk-common-themes/1535 loop14 7:14 0 211.5M 1 loop /var/lib/snapd/snap/mesa-2404/143 loop15 7:15 0 225M 1 loop /var/lib/snapd/snap/mesa-2404/44 loop16 7:16 0 174.7M 1 loop /var/lib/snapd/snap/signal-desktop/720 loop17 7:17 0 173.6M 1 loop /var/lib/snapd/snap/signal-desktop/724 loop18 7:18 0 38.7M 1 loop /var/lib/snapd/snap/snapd/21465 loop19 7:19 0 38.8M 1 loop /var/lib/snapd/snap/snapd/21759 loop20 7:20 0 447.4M 1 loop /var/lib/snapd/snap/telegram-desktop/6261 loop21 7:21 0 447M 1 loop /var/lib/snapd/snap/telegram-desktop/6266 sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 110.8G 0 part ├─fedora_localhost--live-root 253:0 0 50G 0 lvm / ├─fedora_localhost--live-swap 253:1 0 7.9G 0 lvm [SWAP] └─fedora_localhost--live-home 253:2 0 52.9G 0 lvm /home sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 0 128M 0 part └─sdb2 8:18 0 931.4G 0 part /crypt sdc 8:32 1 0B 0 disk sdd 8:48 1 0B 0 disk sde 8:64 1 0B 0 disk sdf 8:80 1 0B 0 disk sdg 8:96 1 0B 0 disk sdh 8:112 1 0B 0 disk sdi 8:128 1 0B 0 disk sdj 8:144 1 0B 0 disk sr0 11:0 1 1024M 0 rom zram0 252:0 0 7.7G 0 disk [SWAP]
Output of df -h: ilesystem Size Used Avail Use% Mounted on /dev/mapper/fedora_localhost--live-root 49G 47G 396M 100% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 1.9M 1.6G 1% /run /dev/loop0 128K 128K 0 100% /var/lib/snapd/snap/bare/5 /dev/loop1 56M 56M 0 100% /var/lib/snapd/snap/core18/2829 /dev/loop3 75M 75M 0 100% /var/lib/snapd/snap/core22/1621 /dev/loop2 56M 56M 0 100% /var/lib/snapd/snap/core18/2846 /dev/loop4 74M 74M 0 100% /var/lib/snapd/snap/core22/1663 /dev/loop5 67M 67M 0 100% /var/lib/snapd/snap/core24/490 /dev/loop6 67M 67M 0 100% /var/lib/snapd/snap/core24/609 /dev/loop7 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/194 /dev/loop8 165M 165M 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198 /dev/loop9 505M 505M 0 100% /var/lib/snapd/snap/gnome-42-2204/172 /dev/loop10 506M 506M 0 100% /var/lib/snapd/snap/gnome-42-2204/176 /dev/loop11 403M 403M 0 100% /var/lib/snapd/snap/gnome-46-2404/42 /dev/loop12 407M 407M 0 100% /var/lib/snapd/snap/gnome-46-2404/48 /dev/loop13 92M 92M 0 100% /var/lib/snapd/snap/gtk-common-themes/1535 /dev/loop14 212M 212M 0 100% /var/lib/snapd/snap/mesa-2404/143 /dev/loop15 225M 225M 0 100% /var/lib/snapd/snap/mesa-2404/44 /dev/loop16 175M 175M 0 100% /var/lib/snapd/snap/signal-desktop/720 /dev/loop17 174M 174M 0 100% /var/lib/snapd/snap/signal-desktop/724 /dev/loop18 39M 39M 0 100% /var/lib/snapd/snap/snapd/21465 /dev/loop20 448M 448M 0 100% /var/lib/snapd/snap/telegram-desktop/6261 /dev/loop19 39M 39M 0 100% /var/lib/snapd/snap/snapd/21759 /dev/loop21 448M 448M 0 100% /var/lib/snapd/snap/telegram-desktop/6266 tmpfs 3.9G 68K 3.9G 1% /tmp /dev/sdb2 916G 313G 557G 36% /crypt /dev/sda1 974M 358M 549M 40% /boot /dev/mapper/fedora_localhost--live-home 52G 1.7G 48G 4% /home tmpfs 794M 152K 794M 1% /run/user/1000
Output of du -xk / | sort -n -k1 | tail -20: 3055132 /var/lib/flatpak 3145220 /var/cache/abrt-di/usr/lib/debug/usr 3317376 /var/cache/abrt-di/usr/lib/debug 3317380 /var/cache/abrt-di/usr/lib 3405388 /var/cache/abrt-di/usr 3405392 /var/cache/abrt-di 3602180 /usr/lib 3683844 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4/packages 3720924 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4 5532256 /var/cache/dnf 5741152 /var/lib/snapd 5762344 /var/lib/dnf/system-upgrade 5816828 /var/lib/dnf 6108620 /usr/share 6801300 /usr/lib64 9175600 /var/cache 15815688 /var/lib 18315588 /usr 27260332 /var 48248356 /
Another thing: in my search of Linux partitioning tools I discovered, on the site Geeks for Geeks, two GUI partition management tools that allegedly offer "data integrity," meaning I could repartition a device without losing data on the partition(s) affected by the repartitioning operation. The ones recommended to me are GParted and the KDE partition manager. I am running in a KDE environment. Would anyone recommend either of those two partitioning tools?
Temlakos
On Sun, Nov 10, 2024 at 6:59 AM Will McDonald wmcdonald@gmail.com wrote:
If you can, show people actual command outputs, it'll make it easier to help.
Do you have any flex with LVM or are your filesystems directly on block devices? e.g.
root@fedora:~# pvs; vgs; lvs
Review your mounts/filesystems, e.g.:
root@fedora:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS zram0 252:0 0 8G 0 disk [SWAP] nvme0n1 259:0 0 953.9G 0 disk ├─nvme0n1p1 259:1 0 600M 0 part /boot/efi ├─nvme0n1p2 259:2 0 1G 0 part /boot └─nvme0n1p3 259:3 0 952.3G 0 part /home / root@fedora:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p3 953G 136G 817G 15% / devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 16G 84K 16G 1% /dev/shm efivarfs 246K 47K 195K 20% /sys/firmware/efi/efivars tmpfs 6.3G 2.3M 6.3G 1% /run /dev/nvme0n1p3 953G 136G 817G 15% /home /dev/nvme0n1p2 974M 292M 615M 33% /boot tmpfs 16G 672K 16G 1% /tmp /dev/nvme0n1p1 599M 20M 580M 4% /boot/efi tmpfs 3.2G 12M 3.1G 1% /run/user/1000
Understand where your space is being consumed on the / device. Don't use '-h' so you can sort easily, use 'x' so as to limit your 'du' to a single device. e.g.
root@fedora:~# du -xk / | sort -n -k1 | tail -20 1480504 /usr/lib/python3.12/site-packages/azure 1561480 /var/spool/abrt/ccpp-2024-04-27-13:17:11.106624-89698 1602284 /opt 2184720 /var/spool 2184720 /var/spool/abrt 2226356 /var/cache 2344592 /usr/lib/python3.12 2344592 /usr/lib/python3.12/site-packages 3429168 /usr/share 4395972 /usr/lib 5354284 /usr/lib64 9976580 /var/lib/flatpak/repo/objects 9980444 /var/lib/flatpak/repo 10041060 /var/lib/flatpak 14354904 /usr 33858716 /var/lib/libvirt/images 33858724 /var/lib/libvirt 44206592 /var/lib 49862812 /var 65976164 /
(Optional, `du -xk / | sort -n -k1 | tac` if you prefer your output the other way round...)
Next, is any of that stuff you don't need? So in my example, I could look at my libvirt images, or flatpacks (which I will, because I'm not specifically using any, to my knowledge.)
Do you have logs you can rotate/archive from /var (if /var's on your / drive rather than its own block device / partition.)
Do you have any Yum cache lying around from old major version upgrades?
What's on the filesystem that *isn't* owned by a package, should it be there?
On Sun, 10 Nov 2024 at 11:23, Terry Hurlbut temlakos@gmail.com wrote:
Everyone:
I have a problem upgrading to Fedora 41. After I download all the packages and import the keys, it's telling me I need around 5 GB more space on the / filesystem. The / system is on a partition that has only 50 GiB total, and 395.2 MiB free. (I use the GiB and MiB symbols deliberately.) Specifically it says I need to find 4437 MB on that system. If I have to repartition, I understand that I might as well do a fresh install. My data is safe enough - it's on a completely different physical device, mounted as /crypt - and another petition on the "root device" is present with 47.4 GiB free (there's nothing on it but the contents of /home). But I can't remember half the stuff I installed from non-core repositories like rpmfusion, and if I have to install from scratch, I'll lose a lot of applications. (The kernels are on /boot, which is a 1.0 GiB partition that has more than 500 MiB free.) How can I free up that extra space (say, 5GiB for good measure) without having to reformat the root device for a fresh install?
Temlakos
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Terry Hurlbut composed on 2024-11-10 06:23 (UTC-0500):
I have a problem upgrading to Fedora 41. After I download all the packages and import the keys, it's telling me I need around 5 GB more space on the / filesystem. The / system is on a partition that has only 50 GiB total, and 395.2 MiB free. (I use the GiB and MiB symbols deliberately.) Specifically it says I need to find 4437 MB on that system. If I have to repartition, I understand that I might as well do a fresh install. My data is safe enough - it's on a completely different physical device, mounted as /crypt - and another petition on the "root device" is present with 47.4 GiB free (there's nothing on it but the contents of /home). But I can't remember half the stuff I installed from non-core repositories like rpmfusion, and if I have to install from scratch, I'll lose a lot of applications. (The kernels are on /boot, which is a 1.0 GiB partition that has more than 500 MiB free.) How can I free up that extra space (say, 5GiB for good measure) without having to reformat the root device for a fresh install?
This is an expected consequence of filling a filesystem with packages before installing any, and deleting none before installing all. It tends to destroy filesystem efficiency via massive fragmenting.
This has happened to me often. I deal with it via rpm. Goto your cache directory with the most rpms in it after logging in as root in multi-user.target. Long list the files by size, smallest first. Use rpm to force upgrade (rpm -Uvh --nodeps) the largest rpm that is not in use while in multi-user.target. This will usually be something related to your DE or X, such as themes, icons, fonts, wallpapers, X/Wayland components and such, or LibreOffice, GIMP, or web engines/browsers, then remove that rpm and check freespace. Once freespace reaches the value reported to be needed by dnf, do one more, then you can expect to finish normally using dnf.
If you start with the biggest rpm and get a not enough space response, choose some less huge rpm(s) to start with.
If a kernel rpm group is among your cached packages, you can probably add kernel* to your excludes= line in /etc/dnf/dnf.conf, move the kernel rpms to some other filesystem, do the upgrade, dnf clean packages, move kernel rpms back to cache, remove kernel* from dnf.conf, then do dnf upgrade once more to complete the upgrade.
On Sun, 10 Nov 2024 at 12:21, Terry Hurlbut temlakos@gmail.com wrote:
Answers to Will's questions: At least 4437 MB more space required on the / filesystem.
Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
<snip> sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 110.8G 0 part ├─fedora_localhost--live-root 253:0 0 50G 0 lvm / ├─fedora_localhost--live-swap 253:1 0 7.9G 0 lvm [SWAP] └─fedora_localhost--live-home 253:2 0 52.9G 0 lvm /home sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 0 128M 0 part └─sdb2 8:18 0 931.4G 0 part /crypt
Both your / and /home are on LVM, that might give you some options to juggle. What's the output of
# pvs # vgs # lvs
Output of df -h:
ilesystem Size Used Avail Use% Mounted on /dev/mapper/fedora_localhost--live-root 49G 47G 396M 100% / /dev/mapper/fedora_localhost--live-home 52G 1.7G 48G 4% /home tmpfs 794M 152K 794M 1% /run/user/1000
Output of du -xk / | sort -n -k1 | tail -20: 3055132 /var/lib/flatpak 3145220 /var/cache/abrt-di/usr/lib/debug/usr 3317376 /var/cache/abrt-di/usr/lib/debug 3317380 /var/cache/abrt-di/usr/lib 3405388 /var/cache/abrt-di/usr 3405392 /var/cache/abrt-di
According to https://unix.stackexchange.com/a/130802 that /var/cache/abrt-di can be cleared down, that'll get you ~3.5GiB.
3602180 /usr/lib 3683844 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4/packages 3720924 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4 5532256 /var/cache/dnf 5741152 /var/lib/snapd 5762344 /var/lib/dnf/system-upgrade 5816828 /var/lib/dnf 6108620 /usr/share 6801300 /usr/lib64 9175600 /var/cache 15815688 /var/lib 18315588 /usr 27260332 /var 48248356 /
"yum clean all" might claw back a little more space if the upgrade binaries are stored separately?
Another thing: in my search of Linux partitioning tools I discovered, on
the site Geeks for Geeks, two GUI partition management tools that allegedly offer "data integrity," meaning I could repartition a device without losing data on the partition(s) affected by the repartitioning operation. The ones recommended to me are GParted and the KDE partition manager. I am running in a KDE environment. Would anyone recommend either of those two partitioning tools?
I'd look at LVM before starting to mess with moving/resizing partition boundaries. I didn't actually check which file systems are on your devices, what does the following show:
# df -Tk
You could steal some space from /home and reallocate to / following: https://unix.stackexchange.com/questions/213245/increase-root-partition-by-r...
Here are the outputs of the various other commands you recommended I run:
sudo pvs: PV VG Fmt Attr PSize PFree /dev/sda2 fedora_localhost-live lvm2 a-- <110.79g 0
sudo vgs VG #PV #LV #SN Attr VSize VFree fedora_localhost-live 1 3 0 wz--n- <110.79g 0
sudo lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home fedora_localhost-live -wi-ao---- 52.87g root fedora_localhost-live -wi-ao---- 50.00g swap fedora_localhost-live -wi-ao---- 7.91g
sudo df -Tk Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/mapper/fedora_localhost--live-root ext4 51290592 48248260 404508 100% / devtmpfs devtmpfs 4096 0 4096 0% /dev tmpfs tmpfs 4061620 0 4061620 0% /dev/shm tmpfs tmpfs 1624652 1888 1622764 1% /run /dev/loop0 squashfs 128 128 0 100% /var/lib/snapd/snap/bare/5 /dev/loop1 squashfs 57088 57088 0 100% /var/lib/snapd/snap/core18/2829 /dev/loop3 squashfs 76032 76032 0 100% /var/lib/snapd/snap/core22/1621 /dev/loop2 squashfs 56704 56704 0 100% /var/lib/snapd/snap/core18/2846 /dev/loop4 squashfs 75648 75648 0 100% /var/lib/snapd/snap/core22/1663 /dev/loop5 squashfs 67840 67840 0 100% /var/lib/snapd/snap/core24/490 /dev/loop6 squashfs 67840 67840 0 100% /var/lib/snapd/snap/core24/609 /dev/loop7 squashfs 168832 168832 0 100% /var/lib/snapd/snap/gnome-3-28-1804/194 /dev/loop8 squashfs 168832 168832 0 100% /var/lib/snapd/snap/gnome-3-28-1804/198 /dev/loop9 squashfs 516352 516352 0 100% /var/lib/snapd/snap/gnome-42-2204/172 /dev/loop10 squashfs 517248 517248 0 100% /var/lib/snapd/snap/gnome-42-2204/176 /dev/loop11 squashfs 412032 412032 0 100% /var/lib/snapd/snap/gnome-46-2404/42 /dev/loop12 squashfs 416128 416128 0 100% /var/lib/snapd/snap/gnome-46-2404/48 /dev/loop13 squashfs 93952 93952 0 100% /var/lib/snapd/snap/gtk-common-themes/1535 /dev/loop14 squashfs 216576 216576 0 100% /var/lib/snapd/snap/mesa-2404/143 /dev/loop15 squashfs 230400 230400 0 100% /var/lib/snapd/snap/mesa-2404/44 /dev/loop16 squashfs 178944 178944 0 100% /var/lib/snapd/snap/signal-desktop/720 /dev/loop17 squashfs 177920 177920 0 100% /var/lib/snapd/snap/signal-desktop/724 /dev/loop18 squashfs 39680 39680 0 100% /var/lib/snapd/snap/snapd/21465 /dev/loop20 squashfs 458240 458240 0 100% /var/lib/snapd/snap/telegram-desktop/6261 /dev/loop19 squashfs 39808 39808 0 100% /var/lib/snapd/snap/snapd/21759 /dev/loop21 squashfs 457856 457856 0 100% /var/lib/snapd/snap/telegram-desktop/6266 tmpfs tmpfs 4061624 640 4060984 1% /tmp /dev/sdb2 ext4 960173080 328045408 583279800 36% /crypt /dev/sda1 ext4 996780 366208 561760 40% /boot /dev/mapper/fedora_localhost--live-home ext4 54253864 1774744 49690768 4% /home tmpfs tmpfs 812324 152 812172 1% /run/user/1000
Output of sudo yum clean all 988 files removed
And now, using Dolphin, I find that the / LV no longer has that concerning red line, and is showing 5.6 GiB free.
Have I just freed up the space I need? Or did I do no more than remove the upgrade binaries that were all I had room to store before everything ran out of space? Just how much space do the dnf upgrade packages take up for a Fedora 40->41 upgrade?
How would you advise reclaiming some of the space I allocated to /home without needing to? (The /home partition mostly contains symlinks referring to directories that I store on /crypt. The /crypt petition is a 1 TB SDD with plenty of space; that's for data only.)
If I can have a walk-through to manage readjusting between / and /home without using parted or GParted, somebody could do me a really big favor. (I already know NOT to use fdisk!)
Temlakos
On Sun, Nov 10, 2024 at 8:05 AM Will McDonald wmcdonald@gmail.com wrote:
On Sun, 10 Nov 2024 at 12:21, Terry Hurlbut temlakos@gmail.com wrote:
Answers to Will's questions: At least 4437 MB more space required on the / filesystem.
Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
<snip> sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 110.8G 0 part ├─fedora_localhost--live-root 253:0 0 50G 0 lvm / ├─fedora_localhost--live-swap 253:1 0 7.9G 0 lvm [SWAP] └─fedora_localhost--live-home 253:2 0 52.9G 0 lvm /home sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 0 128M 0 part └─sdb2 8:18 0 931.4G 0 part /crypt
Both your / and /home are on LVM, that might give you some options to juggle. What's the output of
# pvs # vgs # lvs
Output of df -h: ilesystem Size Used Avail Use% Mounted on /dev/mapper/fedora_localhost--live-root 49G 47G 396M 100% / /dev/mapper/fedora_localhost--live-home 52G 1.7G 48G 4% /home tmpfs 794M 152K 794M 1% /run/user/1000
Output of du -xk / | sort -n -k1 | tail -20: 3055132 /var/lib/flatpak 3145220 /var/cache/abrt-di/usr/lib/debug/usr 3317376 /var/cache/abrt-di/usr/lib/debug 3317380 /var/cache/abrt-di/usr/lib 3405388 /var/cache/abrt-di/usr 3405392 /var/cache/abrt-di
According to https://unix.stackexchange.com/a/130802 that /var/cache/abrt-di can be cleared down, that'll get you ~3.5GiB.
3602180 /usr/lib 3683844 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4/packages 3720924 /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4 5532256 /var/cache/dnf 5741152 /var/lib/snapd 5762344 /var/lib/dnf/system-upgrade 5816828 /var/lib/dnf 6108620 /usr/share 6801300 /usr/lib64 9175600 /var/cache 15815688 /var/lib 18315588 /usr 27260332 /var 48248356 /
"yum clean all" might claw back a little more space if the upgrade binaries are stored separately?
Another thing: in my search of Linux partitioning tools I discovered, on the site Geeks for Geeks, two GUI partition management tools that allegedly offer "data integrity," meaning I could repartition a device without losing data on the partition(s) affected by the repartitioning operation. The ones recommended to me are GParted and the KDE partition manager. I am running in a KDE environment. Would anyone recommend either of those two partitioning tools?
I'd look at LVM before starting to mess with moving/resizing partition boundaries. I didn't actually check which file systems are on your devices, what does the following show:
# df -Tk
You could steal some space from /home and reallocate to / following: https://unix.stackexchange.com/questions/213245/increase-root-partition-by-r...
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On Sun, 10 Nov 2024 at 20:48, Terry Hurlbut temlakos@gmail.com wrote:
Output of sudo yum clean all 988 files removed
And now, using Dolphin, I find that the / LV no longer has that concerning red line, and is showing 5.6 GiB free.
Have I just freed up the space I need?
Do you still have ~3GiB of stuff in /var/lib/dnf/system-upgrade/fedora-7efbab3c1dbcd0d4 (or ~5.6GiB in 5762344 /var/lib/dnf/system-upgrade?)
If so you could retry " dnf system-upgrade download --releasever=41 --allowerasing"
... and just see if you still get the warning/error.
How would you advise reclaiming some of the space I allocated to /home
without needing to? (The /home partition mostly contains symlinks referring to directories that I store on /crypt. The /crypt petition is a 1 TB SDD with plenty of space; that's for data only.)
If I can have a walk-through to manage readjusting between / and /home without using parted or GParted, somebody could do me a really big favor. (I already know NOT to use fdisk!)
This process is literally in the link here: https://unix.stackexchange.com/questions/213245/increase-root-partition-by-r... (and more briefly here: https://unix.stackexchange.com/a/309723)
In the linked example: 1. Replace /dev/mapper/VolGroup-lv_home with /dev/mapper/fedora_localhost--live-home 2. Replace /dev/mapper/VolGroup-lv_root for /dev/mapper/fedora_localhost--live-root
Your disks / devices are smaller, so
# umount /home # e2fsck -f /dev/mapper/fedora_localhost--live-home # resize2fs /dev/mapper/fedora_localhost--live-home 10G # lvreduce -L 10G /dev/mapper/fedora_localhost--live-home # lvextend -l +100%FREE /dev/mapper/fedora_localhost--live-root # resize2fs /dev/mapper/fedora_localhost--live-root # mount /home
Would move ~40GiB from /home to /. Obviously tweak the numbers to your liking
If you can't unmount /home, fuser or lsof can help identify what's holding files open.
If you're nervous messing with file systems and block devices... I've been doing this off and on for > 20 years and I still think carefully, measure twice, cut once and worry when it comes to disks. Unless I *really* don't give a crap about the machine or its data integrity because it's replaceable.
Backup anything valuable in the blast radius.
Practice on another machine, VM or cloud instance to ensure you're comfortable what's happening.
On Sun, Nov 10, 2024 at 07:20:58AM -0500, Terry Hurlbut wrote:
Answers to Will's questions:
The message, which was the output of dnf system-upgrade download --releasever=41 --allowerasing, ended with:
Error summary:
Disk Requirements:
At least 4437 MB more space required on the / filesystem.
Output of lsblk:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
[snip]
sda 8:0 0 111.8G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 110.8G 0 part ├─fedora_localhost--live-root 253:0 0 50G 0 lvm / ├─fedora_localhost--live-swap 253:1 0 7.9G 0 lvm [SWAP] └─fedora_localhost--live-home 253:2 0 52.9G 0 lvm /home sdb 8:16 0 931.5G 0 disk ├─sdb1 8:17 0 128M 0 part └─sdb2 8:18 0 931.4G 0 part /crypt
[snip]
Output of df -h: ilesystem Size Used Avail Use% Mounted on /dev/mapper/fedora_localhost--live-root 49G 47G 396M 100% /
[snip]
/dev/sdb2 916G 313G 557G 36% /crypt /dev/sda1 974M 358M 549M 40% /boot /dev/mapper/fedora_localhost--live-home 52G 1.7G 48G 4% /home
[snip]
Both LV's swap and home have sufficient space for your 5GB needs. I can envision 2 approaches:
1) reallocate LV swap extents to LV root: - create an 8GB file on /home and use it a swap - stop using the LV swap as swap and return its extents to the VG pool - lvresize (or lvextend) the LV root and resize the root fs
2) shrink LV home and reallocate the extents to LV root - copy the contents of /home (< 2GB) to somewhere on /crypt - reduce the home filesystem by what, ?10,20,30GB? Your choice - resize the LV home to match (I think lvresize can do both) - enlarge the LV root and the root fs to match (again I think lvresize can do both)
On 11 Nov 2024, at 01:38, Jon LaBadie jonfu@jgcomp.com wrote:
- reallocate LV swap extents to LV root:
- create an 8GB file on /home and use it a swap
- stop using the LV swap as swap and return its extents to the VG pool
- lvresize (or lvextend) the LV root and resize the root fs
On modern Fedora using a disk swap file is no longer the normal setup.
You can use the zram swap instead.
Once you have the zram swap setup then you can delete the swap LV and add its space to your root.
You may already have zram setup.
What do these report:
sudo swapon sudo zramctl
For example this is what I see:
$ sudo swapon NAME TYPE SIZE USED PRIO /dev/zram0 partition 8G 0B 100 $ sudo zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram0 lzo-rle 8G 4K 80B 12K 20 [SWAP]
On an older system I see both disk and ram swap:
$ sudo swapon NAME TYPE SIZE USED PRIO /dev/dm-3 partition 7.8G 0B -2 /dev/zram0 partition 8G 256K 100
First you would need to remove swap from your /etc/fstab and reboot. Then you should be able to delete the swap partition and grow your root partition.
Barry
-
Barry Scott -
Felix Miata -
GianPiero Puccioni -
Jon LaBadie -
Patrick O'Callaghan -
Terry Hurlbut -
Will McDonald