Comment # 2 on bug 1202952 from William Brown

(In reply to Adrian Schr���ter from comment #1)
> I suppose your sources have no constraints for required disk space?

I have never needed one on any other architecture. 

> 
> How much disk space do they need according to the statistics file?

There is no such thing as a "statistics file".

home:firstyear:branches:network:ldap/ # find . | grep -i stat
home:firstyear:branches:network:ldap/ #


This affects many packages I maintain, but lets use 389-ds as an example. Doing
a du -h on a build root shows that it only needs 2.4G for a completed build,
including all installed packages and compiled artefacts.

However the only way to make the build reliable is to request a constraints of
25G. This appears to be because OBS selects the constraints based on maximum
capacity of the disk, not the amount of disk reserved for a build.
Additionally, because OBS shares builders, that disk amount of 25G has to also
account for potentially other builds going on at the same time AND the actually
installed host itself.

I think that if I build only needs 2.4G, and it somehow is able to trigger
"disk out of space errors" there is a significant issue in the builders
configuration. Does it need more disk? Does a _constraint for size need to
change to represent the amount of space the build actually will need?
Regardless, the fact that these out of space errors are so common, indicates to
me that other people are likely having this issue, but aren't reporting it. It
also indicates that monitoring of the builders in our fleet for disk usage
errors is probably lacking because this should have been noticed before I am
reporting it.