[SOLVED] 19.1.7 update fails - disk full

[chemlud]

Hi!

Tryingto update a 4GB Cf-card install of 386 nano (currently on 19.1.4), but after downloading all updates the install process gives "disk full" and update fails...

Any ideas?

[chemlud]

Tried 4-5 more times, always stops with disk full when installing ruby. But in Dashboard disk is only 33% used. Very strange.

[hbc]

The packages are compressed. Did you try to download and extract the ruby package on other pc? Is the extracted size + the size of all downloaded update packages smaller than your free diskspace?

[chemlud]

32% of 4 GB means roughly 2.6 GB free, do you really think there are packages of that size?

Additional info:

RAM = 2 GB

/var is on disk, /temp in RAM

I tried to reboot the system with /var in RAM, but it never came back (mixed system, as some updates had been done already). Have a dd-copy of the functional card (before updating) and now I'm ready for next try. Better to have /var and /temp in memory?

[chemlud]

...total download for this update is 163 MiB, so not really sure there will be coming out something with more than 1 GiB size?

[chemlud]

Next try with /var  and /tmp in RAM, same result:

[franco]

Uh, oh: https://github.com/opnsense/changelog/blob/9473107466ada781911c6a9a8c353f9c8ee9ee9c/doc/19.1/19.1.7#L11-L14

If you have ruby try to deinstall the plugins using it to salvage a bit of free space first. Then upgrade and try to reinstall the plugins:

$ git grep 'PLUGIN_DEPENDS.*ruby'
benchmarks/iperf/Makefile:PLUGIN_DEPENDS=               iperf3 ruby
net/frr/Makefile:PLUGIN_DEPENDS=                frr6 ruby
security/tor/Makefile:PLUGIN_DEPENDS=           tor ruby

It might be that pkg does something weird in /var and /tmp so the best option is to *not* use RAM MFS in these scenarios, because 1G may be a bit small...


Cheers,
Franco

[chemlud]

Plugins can be uninstalled how? :-)

[monstermania]

FYI
My x64 Nano OPNsense (Intel Atom D525, 2 GB RAM, 8 GB CF-Card) updated without any problems to 19.1.7.

• /var and /tmp in RAM
• only ftpproxy-plugin installed

[chemlud]

...so only apparent difference is size of CF-card? (and 64bit board)

But as the little machines are end-of-life for opnsense by the end of the year I don't want to buy larger cards now. Don't use CF-cards anymore in other devices.

[chemlud]

@franco

dyndns, tucan and wol ar the only plugins installed by me on this system. No way to remove any preinstalled plugins, or?

PS: Tried with /var and /tmp on disk, not in RAM, same result....

[ky41083]

You're probably out of inodes, like me.

Code: [Select]

df -ih

Code: [Select]

dmesg should show something to the effect of:

Code: [Select]

pid 62215 (pkg-static), uid 0 inumber 16868 on : out of inodes
Nano install, 4GB disk. This is irritating to say the least...

Pretty sure we cannot expand this, even in single user mode. Best course of action here, devs?

[ky41083]

Is it possible to specify inodes at some point in the ISO installer? Or does the ISO installer format with more UFS inodes by default than the NANO disk image was created with?

Please, please bump up the inode count in the NANO image I have 1 plugin installed, DynDNS. Can't remember which OPNsense version I started with, but it has been at least 1 year since I setup this install, applied pretty much every update over the course. I would say that this is an undesired usage pattern for resulting in total system breakdown

[chemlud]

Are we really the only two users in the whole wide world with thisproblem? :-/

[franco]

You can deinstall ruby easily, not sure how it ended up there:

# pkg remove ruby

Do you have /usr/ports on your install? I remember you building Unbound...

Yes, no inodes is an issue... a lot of small files will "fill" your system even though space is not an issue. Find the lots of files and delete them.


Cheers,
Franco