maximize-build-space
maximize-build-space copied to clipboard
easimon
temp and root partition swapped
For two weeks or so the root partition and the temp partition has been swapped on around 20% of the runners.
Which results in temp getting bigger and root staying small:
/dev/root 73G 73G 100M 100% /
Please see https://github.com/easimon/maximize-build-space/issues/39#issuecomment-1935591779
Can this be an explanation for what you see?
The tmpfs you mentioned is not the temp partition, but a ramdisk, mounted to /tmp. The temp disk should be mounted at /mnt.
Thank you!
Yes, that's probably it. However, I'm confused on what the fix is. Whatever I specify in temp-reserve-mb will end up getting added to /dev/root.
But if try to make temp-reserve-mb very large (4096) it'll throw fallocate: invalid length value specified.
What are you trying to achieve? The action combines all free space on / and /mnt into an lvm volume, which is then mounted as the workspace directory. The workspace is the place where most build jobs require the most space.
The reserve parameters are to control how much space is not consumed by the lvm volume, so you can still add files outside the workspace... E.g. to download docker images, install further packages via apt-get etc.
By increasing the reserve, you decrease the amount available in the workspace folder.
The temp reserve is something you should seldomly need to adjust, since by default nothing (I know of) writes to /mnt.
I'm getting this too: fallocate: invalid length value specified.
What I think @michabp is suggesting is: check if /mnt mountpoint really exists and do the calculations accordingly, otherwise its inconsistent for both configurations.
If we reserve space on /mnt and / but /mnt doesn't really exist, the reserve total space should be merged, so that it doesn't underflow/overflow on our situation, which is exactly what is happening right now.
It used to be 20% of the runners but now its almost all runners, from my experience.
I added #48, which to my knowledge describes the general situation: provided disk space and layout is fluctuating. Closing this.