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 <wmcdon...@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 <temla...@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-le...@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-le...@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 > -- Temlakos <temla...@gmail.com>
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@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