topic Re: Import 82.10 to MHO 140, space issues. in Hyperscale Firewall (Maestro)

Import 82.10 to MHO 140, space issues.

Ben138019 — Tue, 10 Mar 2026 19:19:05 GMT

Hello,

I am running into an issue where i am receiving an error when i attempt to import the 82.10 464 package in gaia. It is throwing the following: "Error: not enough space The sessions will be terminated. Press Ok to proceed"

The package shows about 5.4gb. /var/log is showing i have 6.4GB free. Is there a certain amount of space above the package size that i need to free up? what am i missing here?

Thank you,

Re: Import 82.10 to MHO 140, space issues.

Lesley — Tue, 10 Mar 2026 21:46:23 GMT

Maybe that is the size before it is unpacked? Anyway check out my old post and the solution provided by a member here to extend the disk with lvm manager

https://community.checkpoint.com/t5/Hyperscale-Firewall-Maestro/Maestro-Orchestrator-140-disk-space/m-p/245672/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufE05MklNU0sxTDVXUFR8MjQ1NjcyfFNVQlNDUklQVElPTlN8aEs#M3285

Re: Import 82.10 to MHO 140, space issues.

yukaia — Tue, 10 Mar 2026 22:05:16 GMT

I'm still flabbergasted that they only ship the orchestrators with 128gb ssds.

Just as a side note, if you have physical/local access stick to using lvm_manager, avoid going the route of lvresize and xfs_growfs. It's really easy to shoot yourself in the foot with those commands, only use them if you can't get physical/local access to the orchestrator, and only grow it by a few GB, otherwise you won't be able to take any snapshots, and you'll have to perform a clean install to fix the partition sizes because you can't shrink an xfs partition.

Re: Import 82.10 to MHO 140, space issues.

Ben138019 — Wed, 11 Mar 2026 10:59:30 GMT

I need to know how much space to give it once in the LVM manager. There is only so much space available under the unnallocated space and i am getting close to being unable to move any additional space to /var/log. I understand we should leave the unnallocated space at approximately 120% of what lv_current has. realistically I can only move 1GB more and have the recommended space in unallocated for snapshots. I would like to know how close i am to the needed free amount so i can decide if i should use the LVM to resize the additional gig or continue to hunt and delete logs. Thank you

Re: Import 82.10 to MHO 140, space issues.

Lesley — Wed, 11 Mar 2026 17:41:13 GMT

It depends on some factors, you can try to make snapshot and check how much space it takes based on that you can rearrange the disk space. I can share a df -h tomorrow from an orchestrator.

Alternative is a clean install, at one point you have to because the disk is small. In future releases they optimized it a bit more that old packages will be cleanup i think, but cannot find the post anymore regarding this

Re: Import 82.10 to MHO 140, space issues.

Ben138019 — Thu, 12 Mar 2026 10:52:55 GMT

Support was able to tell me that I would need 2x the ammount of space in /var/log/ of the package I'm importing. so for this package, I will need at least 10.8gb free to import the package.

Re: Import 82.10 to MHO 140, space issues.

Lesley — Thu, 12 Mar 2026 11:43:16 GMT

Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_splat-lv_current 20G 11G 9.3G 54% /
/dev/sda1 290M 87M 188M 32% /boot
tmpfs 7.7G 51M 7.7G 1% /dev/shm
/dev/mapper/vg_splat-lv_log 25G 14G 12G 55% /var/log