Free space required for upgrade

JonH

The upgrade to 25.05-1 completed and I found that it was not done. I am wondering about free space required to do that upgrade.

I suppose the amount of freespace required varies based on pkgs installed.
I have an SG-5100 and 4 days ago (the last time I checked) I had 1.8 GB free space. My biggest space-eaters are the logs of pfBlockerng-devel & ntopng.

My install completed and upon restarting the GUI I find that the install is still available for me. I did it again and after waiting forever, but probably a bit more than 10 minutes later it finally restarted as a complete install. Looking at upgrade_log.latest.txt, there is a line "The process will require 4 MiB more space." This is the first time I experienced this issue and since the 5100 comes with only 4GB I guess it makes sense to clean up the log files before upgrading.

It would be nice to have a reminder to do so (I'm just a home user not a pro). I'm hoping someone can take these comments to heart (assuming I am even correct by assuming that it is a free space issue) and mention free space necessary.

I also wonder if the above is my own misunderstanding and that perhaps the upgrade required 2 separate actions and what I experienced is normal. If that is true I missed that in the notes.

Gertjan

@jonh said in Free space required for upgrade:

I had 1.8 GB free space

and

"The process will require 4 MiB more space."

Lets image every future upgrade takes 10 MiB more.
You'll be fine for another 1800/10 = 180 upgrades, or, with 3 upgrades a year, some 60 years or so.

@jonh said in Free space required for upgrade:

My biggest space-eaters are the logs of pfBlockerng-devel & ntopng.

Keep track of their log files and you'll be fine.

stephenw10

The 5100 has 8GB or eMMC which is usually more than sufficient.

If it ran out of filesystem space it's usually pretty vocal about it. I would expect to see many 'filesystem full' errors logged.

Steve

JonH

@stephenw10
Running out of space was my best guess. Hardly surprising that I made a bad guess, and yes, I'm at 8GB, not 4GB as incorrectly posted.

Here is a snippet that mentions needing more space. In the future I'll try to remember to trim various log files. Between a few years of upgrading first a 2400 and now the 5100 I've never run into this sort of thing.

Number of packages to be removed: 1
Number of packages to be installed: 7
Number of packages to be upgraded: 74
Number of packages to be reinstalled: 138

The process will require 4 MiB more space.
[1/220] Upgrading pcre2 from 10.36 to 10.37...
[1/220] Extracting pcre2-10.37: .......... done

In reviewing the upgrade log file more carefully I find this near the end.

>>> Setting vital flag on pfSense-upgrade... done.
>>> Upgrading necessary packages... 
Checking for upgrades (4 candidates): .... done
Processing candidates (4 candidates): .... done
Checking integrity... done (0 conflicting)
The following 4 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-pkg-Avahi: 2.1_1 -> 2.2 [pfSense]
	pfSense-pkg-mailreport: 3.6.3_2 -> 3.6.3_3 [pfSense]
	pfSense-pkg-openvpn-client-export: 1.6 -> 1.6_2 [pfSense]
	pfSense-pkg-syslog-ng: 1.15_7 -> 1.15_9 [pfSense]

Number of packages to be upgraded: 4
[1/4] Upgrading pfSense-pkg-syslog-ng from 1.15_7 to 1.15_9...

So I guess the upgrade was required to be run a second time and that is normal, but for me unexpected.

stephenw10

I wouldn't expect you to have to run an upgrade more than once. It may have updated the pkg repo itself and then found newer packages. It should have just done that without requiring any interaction though.

When it says The process will require 4 MiB more space. that just means the updated packages will be 4MB larger than before the update. That's expected and not filesystem space issue.

Steve