On 10/11/25 08:19, Stuart Henderson wrote:
it's likely ok but the more headroom the less chance of running into a
problem.
if it's a previously upgraded system I would check sysclean|grep ^/usr
first as there are easy gains to be had if you haven't cleaned before.
unless you've done something strange then anything sysclean shows in
usr/share, usr/include, usr/libdata will be ok to remove (and indeed
will avoid some potential problems from leaving them around).
unless you have compiled software outside of ports then anything
listed by sysclean in usr/lib also ok to remove (sysclean already
tracks libraries used by packages/installed ports).
even if you can't free up more then I'd give it a try anyway as long
as you have console access (local machine or remote serial console /
idrac / similar).
Hi Stuart,
Ok. I was curious if removing the .gdb file plus the already free space
would be sufficient, but I will investigate sysclean in addition to this
for: /usr.
I haven't done anything unique with the server. I install software from
ports and I always upgrade via sysupgrade. The server in question is
both an e-mail server and a web server. This server runs in a VM, so I
intend to take a snapshot before removing any files from: /usr and then
attempting a sysupgrade. If something goes wrong, I should be able to
roll back.
Looking forward, if I were to create a new server with a disk size of 80
GB, what would be a good partition size for: /usr ? The upgrade notes
have said for a while that a 1.1 GB partition size is required, but it
looks like this should be increased going forward.
Thanks again for all the help - these mailing lists are so helpful!
- J
