Dear All,
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
------------------------------ --------- Error Summary ------------- Disk Requirements: At least 4020MB more space needed on the / filesystem. ---------------------------------------
Any ideas?
Thanks in advance,
Paul
On Sun, 2023-04-30 at 15:23 +0100, Paul Smith wrote:
Dear All,
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
Error Summary
Disk Requirements: At least 4020MB more space needed on the / filesystem.
Any ideas?
It would be useful to know what filesystem you have on /. Some are easier to expand than others. The feasibility also depends on your disk layout, so the output of something like 'lsblk -sf|grep "^sd" would help.
poc
2023-04-30 16:23 UTC+02:00, Paul Smith phhs80@gmail.com:
Dear All,
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
Error Summary
Disk Requirements: At least 4020MB more space needed on the / filesystem.
If you have enough space in another partition, you can use the --downloaddir option. I have vague memories of this having solved the same problem once.
Andras Simon wrote:
If you have enough space in another partition, you can use the --downloaddir option. I have vague memories of this having solved the same problem once.
Though anyone using --downloaddir should be aware that the directory passed as an option is (or was, when it came up last)¹ erased by dnf system-upgrade, so you do not want to pass it a directory like /home. It should be given a directory specifically for the upgrade, so if you put it under /home, make it something like /home/system-upgrade.
¹ https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/... I don't recall if the function or documentation has been improved since that discussion. It's certainly a painful 'gotcha' to stumble upon.
On 4/30/23 07:23, Paul Smith wrote:
Dear All,
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
Error Summary
Disk Requirements: At least 4020MB more space needed on the / filesystem.
Why does it need more than 4 gigabytes to upgrade from f37 to f38? That's just crazy. I'd look into that before I started trying to stretch partitions.
Mike Wright
On Sun, Apr 30, 2023 at 5:40 PM Mike Wright nobody@nospam.hostisimo.com wrote:
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
Error Summary
Disk Requirements: At least 4020MB more space needed on the / filesystem.
Why does it need more than 4 gigabytes to upgrade from f37 to f38? That's just crazy. I'd look into that before I started trying to stretch partitions.
Thanks for all replies.
I have meanwhile been able to do the upgrade, by removing cache files, old kernels, the files in the trash bin and also by running
sudo journalctl --vacuum-size=50M
Paul
On Sun, 2023-04-30 at 09:40 -0700, Mike Wright wrote:
Why does it need more than 4 gigabytes to upgrade from f37 to f38? That's just crazy. I'd look into that before I started trying to stretch partitions.
It'd need to download all the new packages it's going to install, while you still have all the previously installed files. So I'd expect it to be a substantial size. Especially if it had to deal with someone who's installed everything and the kitchen sink. That said, I wonder is it downloading RPMs, or is it fetching an install image?
I gave up doing upgrades, many years ago, there was so many problems with it: It took absolutely ages (it assesses the current system, finds out everything that needs to be installed, downloads it, installs it piece by piece). Conflicts needed resolving, some not very straight-forward to handle. Backups ought to be made. And you still had to assess and fix things up afterwards. It was like some kind of torture.
My preference is to remove the current drive, fit a new blank one, install fresh to it. Check it works, set it up. Then, once happy with it, plug in the old drive, and copy over the files you want to keep. Unplug the old drive and store it for the next upgrade time (it'll be the new drive to swap in). I've always found that massively quicker than upgrading.
Granted, my situation is easier than other people's, since I don't have any databases, or the like, that need to be migrated. That kind of thing needs specific management.
For servers, I like the idea of two-drive systems. One drive is system and applications, the other drive is all for data. For an upgrade, unplug the data drive for safety. Swap the system drive and install the new system. Reconnect the data drive.
On Mon, 01 May 2023 03:38:22 +0930 Tim via users wrote:
I gave up doing upgrades, many years ago, there was so many problems with it
I think it has gotten better. When I upgraded my main system, I kept the old one as an emergency backup and tried to keep it identical to the main system so I could swap it back quickly if I had to. I've never needed it as a backup, but I started experimenting with doing upgrades via dnf, and they all seem to have worked well. It does take forever though, and it does download all the rpms it needs for the upgrade first, so it needs a lot of free space.
The last few upgrades I've done have taken about an hour, and run very successfully.
On Sun, Apr 30, 2023 at 2:33 PM Joe Zeff joe@zeff.us wrote:
On 04/30/2023 12:25 PM, Tom Horsley wrote:
It does take forever though, and it does download all the rpms it needs for the upgrade first, so it needs a lot of free space.
So you start it late in the day and let the actual upgrade run overnight. _______________________________________________ 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 Mon, 2023-05-01 at 03:38 +0930, Tim via users wrote:
I gave up doing upgrades, many years ago, there was so many problems with it: It took absolutely ages (it assesses the current system, finds out everything that needs to be installed, downloads it, installs it piece by piece). Conflicts needed resolving, some not very straight-forward to handle. Backups ought to be made. And you still had to assess and fix things up afterwards. It was like some kind of torture.
Mine took about 45 minutes start to finish, not counting the rpmconf step (which you have to do anyway). Obviously YMMV.
poc
Tim via users composed on 2023-05-01 03:38 (UTC+0930):
I gave up doing upgrades, many years ago, there was so many problems with it: It took absolutely ages (it assesses the current system, finds out everything that needs to be installed, downloads it, installs it piece by piece). Conflicts needed resolving, some not very straight-forward to handle. Backups ought to be made. And you still had to assess and fix things up afterwards. It was like some kind of torture.
It's been over 42 months since I last booted a Fedora installer (to a 5.3 kernel). Upgrading Fedora has worked in excess of 100 times here (15 multiboot PCs with it). On faster machines, allocating as much as an hour for the process is a gross excess. On less weighty installations it probably can take under 10 minutes if you don't include POSTing time that on some machines takes longer than booting an OS.
On 5/1/23 01:18, Felix Miata wrote:
It's been over 42 months since I last booted a Fedora installer (to a 5.3 kernel). Upgrading Fedora has worked in excess of 100 times here (15 multiboot PCs with it). On faster machines, allocating as much as an hour for the process is a gross excess. On less weighty installations it probably can take under 10 minutes if you don't include POSTing time that on some machines takes longer than booting an OS.
I will never understand why people are so inclined to restart from scratch with a new install every time. Their systems must be really bad managed to not trust an upgrade. Or may be they have no customization at all to preserve. My personal system was installed with FC3 in 2005 and then continuously upgraded up to currently FC36. (it has even got metamorphosis from i686 to x86_64, something that was considered impossible to do)
Regards.
On Tue, 2 May 2023 10:13:04 +0200 Roberto Ragusa wrote:
I will never understand why people are so inclined to restart from scratch with a new install every time.
I treat it as an opportunity to get rid of stuff I no longer use.
I also keep the previous release around on a different partition in case I need to investigate why something seems different I can boot back into the older fedora.
On Tue, 2023-05-02 at 10:13 +0200, Roberto Ragusa wrote:
I will never understand why people are so inclined to restart from scratch with a new install every time.
Bad experience doing it in the past, and the huge number of times I've read about the problems people have needed help to resolve on this list.
Their systems must be really bad managed to not trust an upgrade.
Nup. And it's not a matter of trust, it's experience of things I didn't want to repeat again. It seriously wasted my time. And without any real good reason to put myself through that again.
Or may be they have no customization at all to preserve.
That's not too far from the truth. I don't customise my system that much. I spend most of the time using it, not tinkering with the desktop.
When it comes to updates/upgrades, it's not just the OS to contend with, but all the applications. You find that some of the new versions don't work with old configurations, and you have to configure them again, anyway.
On 5/2/23 07:40, Tim via users wrote:
On Tue, 2023-05-02 at 10:13 +0200, Roberto Ragusa wrote:
I will never understand why people are so inclined to restart from scratch with a new install every time.
Bad experience doing it in the past, and the huge number of times I've read about the problems people have needed help to resolve on this list.
Where have you seen these huge number of times? I've only seen a few instances on this list and that's a self-selected sample. It's quite rare that someone is going to post about a successful update.
I have upgraded systems hundreds of times with only a very few (single digit) failures that required intervention. And that was generally because of hardware issues like the laptop wasn't actually plugged in and the battery died.
On Tue, May 2, 2023 at 4:13 AM Roberto Ragusa mail@robertoragusa.it wrote:
[...] My personal system was installed with FC3 in 2005 and then continuously upgraded up to currently FC36. (it has even got metamorphosis from i686 to x86_64, something that was considered impossible to do)
That's impressive.
Jeff
On 5/2/23 20:56, Jeffrey Walton wrote:
On Tue, May 2, 2023 at 4:13 AM Roberto Ragusa mail@robertoragusa.it wrote:
[...] My personal system was installed with FC3 in 2005 and then continuously upgraded up to currently FC36. (it has even got metamorphosis from i686 to x86_64, something that was considered impossible to do)
That's impressive.
Not the same hardware, of course. I am calling "system" the filesystem content, so all the functionality and settings. Hardware has changed a lot of times since then, of course.
Regards.
Paul Smith composed on 2023-04-30 15:23 (UTC+0100):
I am trying to use
dnf system-upgrade download --releasever=38
to upgrade from F37 to F38. However, I am getting this error:
Error Summary
Disk Requirements: At least 4020MB more space needed on the / filesystem.
Any ideas?
This happens to me often, though not to such degree. Until dnf makes the report, I don't know how much it needs.
First thing to do is get rid of trash. If you move things to "trash" rather than deleting, and /home isn't on its own filesystem, it's the logical place to start.
Next, clear /var/tmp/ and /var/log and anyplace else you might have unneeded oldies. /var/log/journal/*/ may have a lot of ancient logs that serve no purpose. You can configure excess for autoremoval via /etc/systemd/journald.conf. Whatever is in /var/cache/dnf/ you should no longer need and can remove with dnf clean.
Next, I use an upgrade initialization mini-script to get package management upgrades in place before continuing with the rest. It contains:
dnf upgrade --releasever=38 dnf* rpm* libsol* glib* systemd* fedor* dracu* hawk*
Lastly, locate the largest downloaded rpms and install selected biggies manually using rpm -Uvh --nodeps. Among them are typically graphics firmware, wallpapers, themes & icons, but there are generally some obese others that are perfectly safe to upgrade whilst operating in multi-user mode, anything to do with X, *office, web browsing, etc. After each such upgrade, delete the rpm from the cache. To facilitate the process, navigate to the cache directory using MC. Pretty much anything whose size MC shows with a K or M is candidate to start with. Once you've created however much space dnf reported you need has been freed, finish with dnf.
Another option I often use for system-upgrade is attaching an extra filesystem to /var/lib/dnf/system-upgrade before beginning, a pretty good guarantee against lack of freespace. If you've already downloaded most and they're on /, find a place to move them that isn't, and mount that to /var/lib/dnf/system-upgrade before proceeding with another dnf system-upgrade download attempt. Don't forget to add the location to /etc/fstab before running dnf system-upgrade reboot.
On 4/30/23 10:18, Felix Miata wrote:
Another option I often use for system-upgrade is attaching an extra filesystem to /var/lib/dnf/system-upgrade before beginning, a pretty good guarantee against lack of freespace. If you've already downloaded most and they're on /, find a place to move them that isn't, and mount that to /var/lib/dnf/system-upgrade before proceeding with another dnf system-upgrade download attempt. Don't forget to add the location to /etc/fstab before running dnf system-upgrade reboot.
Before I started using btrfs, /home was a separate filesystem and usually had extra space so I would create /home/system-upgrade and symlink it into /var/lib/dnf. On a couple of systems that had nfs /home, I did as Felix described using a USB flash drive mounted to /var/lib/dnf/system-upgrade.
-
Andras Simon -
Felix Miata -
Jeffrey Walton -
Joe Zeff -
Mike Wright -
murph nj -
Patrick O'Callaghan -
Paul Smith -
Roberto Ragusa -
Samuel Sieb -
Tim -
Todd Zullinger -
Tom Horsley