Project

General

Profile

Actions

Bug #16372

closed

Advise users to release more space before upgrading to 25.07

Added by Sayed Mohammad Badiezadegan 28 days ago. Updated 28 days ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Installer
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:

Description

After upgrading pfSense to version 25.07, I am seeing a firewall-related error and multiple concerns, like /var/cache/pkg usage is high ~300, and root disk usage 73%.

It is because the older snapshots that hold the big /var_cache_pkg and /cf data.

*Suggestion: *
Please advise users to remove their older pfSense OS in the installation steps to release more space:
(For example: --->> zfs destroy pfSense/ROOT/default@2024-08-05-21:03:43-0)

BTW, I attached my status files.


Files

status_output.tgz (396 KB) status_output.tgz Sayed Mohammad Badiezadegan, 08/14/2025 11:52 PM
Actions #1

Updated by Jim Pingle 28 days ago

  • Status changed from New to Rejected
Actions #2

Updated by Sayed Mohammad Badiezadegan 28 days ago

Jim Pingle wrote in #note-1:

The upgrade guide already mentions this specifically.

https://docs.netgate.com/pfsense/en/latest/install/upgrade-guide-prepare.html#check-and-clean-up-zfs-boot-environment

Thank you for your mention, but most users did not go through the user guide before the upgrade. I think it is more useful to show the older boot environments to the users before the process of upgrading. Thank you.

Actions #3

Updated by Jim Pingle 28 days ago

The upgrade guide is mentioned in the release announcement on the blog, and it's the official place to find information about the upgrade process. We cannot repeat all of that info in every copy of the release notes, and there is no reliable way to predict that the next BE will run out of space. We are working on the backend side of that to clean up older BEs automatically, but that's being tracked separately already. Forcing the user to click through BEs at each upgrade would cause more confusion than it would save.

Actions

Also available in: Atom PDF