public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem with ipfire build system
Date: Mon, 09 Dec 2024 13:43:14 +0100	[thread overview]
Message-ID: <d59d96bf-7d5e-4771-ad1c-6a35ce785ded@ipfire.org> (raw)
In-Reply-To: <39CF8BB8-B6D7-47BF-9502-979184DEF43A@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 3612 bytes --]

Hi Michael,

On 09/12/2024 12:48, Michael Tremer wrote:
> Hello Adolf,
> 
>> On 8 Dec 2024, at 12:04, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi Michael,
>>
>> I have experienced a problem yesterday and today with the IPFire build system. Not a major problem but it only seems to have started recently.
>>
>> Today when I tried to run the build command with the standard IPFire-2.x git clone I got the following error message.
>>
>> ./make.sh build
>>
>> ERROR: Not enough temporary space available, need at least 8192MiB, but only have 491 [ FAIL ]
>>      Check /home/ahb/sandbox/ipfire-2.x/log_x86_64/_build.preparation.log for errors if applicable [ FAIL ]
> 
> So, there is a check that will ensure that there is 8 GiB available for the build directory so that (ideally) the build does not abort because of low disk space.
> 
> This is however a little bit of a gamble because we don’t always know exactly how much (temporary) space the build environment might need and it is a little bit difficult if a build is being restarted (because we might have consumed a chunk of the 8 GiB already).
> 
> Could you send me the output of “df -h” and “du -csh build_x86_64” when this problem happens?

I managed to get the same problem to occur. Then running df -h told me where my problem was and it is self made.

My home directory, where the git repo's are in is nearly full. With one repo with a full build directory I only had 4.9G left (99% full) not enough space for the 8G.

When I cleaned the other build directory then my home directory had 14G available (97% full) and so enough space for the 8G.

So I don't currently have enough space for both of the git repos to be getting built.

I will need to search out what is using up the space as normally most things are on my file server, which includes most of my vm definitions. I will need to figure out what has filled up the space over time and either get rid of it or move it elsewhere.

Sorry for the noise.

Regards,
Adolf.

> 
>> I was able to overcome it by running the ./make.sh clean command on the openvpn-2.6-meetup-rebased branch git repo that I also have on my system.
>>
>> After running the clean command the normal ipfire-2.x git repo build command is working fine and no longer gives the above message.
> 
> It sounds like the calculation works well when there is no build directory. That is the easy case.
> 
>> Yesterday it was the other way around. I tried to run the build command on the openvpn-2.6-meetup-rebased branch and got the same sort of message as above just the amount available was a bit different. Something like 670 instead of 491 today. Yesterday, when I ran the clean command on my normal ipfire-2.x git repo then the openvpn-2.6-meetup-rebased git repo had no problem with the build. Just doing a reboot on my desktop machine that has the git repo's on it made no difference.
> 
> Hmm, is it possible that the build environment has gone so large that 8 GiB is exceeded and my calculation goes into negative numbers? That might break things hard.
> 
>> I have not had this problem in the past. Although not a major problem, I have definitely run a build on one repo when the other still had its build results in place so something has changed. Maybe something in Arch Linux with one of the recent updates I ran.
> 
> It shouldn’t. This code was changed when we introduced the containerised build system earlier this year. So I am quite confident that I broke this myself.
> 
> Best,
> -Michael
> 
>> Regards,
>>
>> Adolf.
>>
>>
> 


  reply	other threads:[~2024-12-09 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08 12:04 Adolf Belka
2024-12-09 11:48 ` Michael Tremer
2024-12-09 12:43   ` Adolf Belka [this message]
2024-12-09 13:39     ` Adolf Belka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d59d96bf-7d5e-4771-ad1c-6a35ce785ded@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox