Don't let the disk fill up

[ryandesign (Ryan Carsten Schmidt)]

Bad things happen when the disk is completely full; for example, mpbb doesn't work anymore, so it can't clean things up and free up the disk space again.

Maybe we should take some steps to ensure the disk can't fill up completely. For example, if we presume that installing the port and installing the dependencies are the times when disk usage might grow unbounded, then we might spawn a background process at those times that monitors disk space and kills the port command if disk space gets very low.

[raimue (Rainer Müller)]

I am not convinced this is really worth implementing...

[ryandesign (Ryan Carsten Schmidt)]

Replying to raimue:

I am not convinced this is really worth implementing...

You're not the one who has had to find a buildbot worker in a wedged state requiring someone to manually log into it, free up disk space, and then reschedule dozens of builds that failed because of it. :) Fortunately it hasn't happened often. Usually when a build runs out of disk space, at least a few KB are available for the temp file and it can clean itself up.

I agree it would be better if we simply had more disk space free on each worker so that we didn't run out. There are other open tickets about some ideas I had for that, including #57396 and #57464.

[ryandesign (Ryan Carsten Schmidt)]

The 10.8 builder's disk filled up again today, causing hundreds of builds to fail immediately before we noticed the problem. But it was due to the Spotlight index growing out of control (it was 26GB) (again—we've seen that once before) so I've nuked the Spotlight index again and added /opt and /Applications/MacPorts to the Spotlight exclude list to hopefully keep this from happening again or at least delay it.

[jmroot (Joshua Root)]

In 8f12db95ced35509c22c7d9919220600bf190743/mpbb (master):

cleanup: delete stuff until there's enough space

See: #57464
See: #57869