Upgrade from 24.11 to 25.07.1 fails extracting Python due to disk space

digininja99

In case it makes a difference, this is on a Netgate 1100.

slu

how many old boot environments are saved?
https://docs.netgate.com/pfsense/en/latest/backup/zfsbe/gui.html

I delete before update all expect of the last version.

digininja99

@slu Intersting, I've deleted all but the last two, interestingly, the amount of used space on / hasn't increased, but the size of the disk has.

Before:

[24.11-RELEASE][root@firewall.krynn.int]/cf/conf/backup: df -h
Filesystem                            Size    Used   Avail Capacity  Mounted on
pfSense/ROOT/default                  1.5G    1.1G    385M    75%    /

After:

[24.11-RELEASE][root@firewall.krynn.int]/cf/conf: df -h
Filesystem                            Size    Used   Avail Capacity  Mounted on
pfSense/ROOT/default                  4.4G    1.1G    3.3G    26%    /

I'm running another upgrade now to see what happens.

digininja99

That worked, the upgrade ran fine from the command line after deleting things.

Thanks.

stephenw10

Yup you really want to see at least 1G available there for the upgrade.

digininja99

@stephenw10 can you point me at something else explains why when I deleted files the total disk space got bigger rather than the free space going up? That is something I've not seen before.

To prevent this in the future, is it worth adding a check into the upgrade script to check for available space?

stephenw10

Yes the upgrade could check that. And the ZFS BE manager could also alert the user to limited space And report the actual used space for each BE. That's in progress.

But the values you see there from df show the used and available space inside the current BE only not for the full disk. So when you remove BEs the available total space for other BEs increases.

digininja99

@stephenw10 I've just had a look at boot environments. I know it's not the same but in my head it works like creating a new VM which pushes all the others aside so it can share the available space. Boot the new VM, check it works ok, if so all is good, if not, just boot the pervious.

It seems like a cool idea for making a system that is very stable when it comes to big system updates - as long as there is room for the new environment.

SteveITS

@digininja99 https://docs.netgate.com/pfsense/en/latest/troubleshooting/filesystem-shrink.html

digininja99

@SteveITS Thanks.