Arch Linux

SeagullFish

Member

Registered: 2023-08-10

Posts: 53

[SOLVED] Disk space issues while trying to update electron32

I am having difficulties updating electron32[AUR] (32.3.1-4 -> 32.3.3-1):

[foo@bar ~]$ mkdir Build
[foo@bar ~]$ cd Build
[foo@bar Build]$ git clone https://aur.archlinux.org/electron32.git
[foo@bar Build]$ cd electron32
[foo@bar electron32]$ makepkg -s

This results in a heavy workload for a long time, and then makepkg fails with multiple error outputs like these lines (manually translated to English):

cp: could not create regular file 'src/third_party/dawn/third_party/angle/src/libANGLE/es3_copy_conversion_table_autogen.cpp': No more space available on the device
cp: could not create directory 'src/third_party/dawn/third_party/angle/src/libANGLE/overlay': No more space available on the device

Eventually, makepkg terminates with this output:

==> ERROR: An error occurred in prepare().
    Aborting...

Although the size of the directory ~/Build/electron32 is quite consuming after the makepkg attempt (105.4 GB), there is still more than 50 GB available of free disk space. So I don't understand why the attempt failed this soon.
Nevertheless, I moved the whole directory to an (empty) external device, and tried running makepkg again from there. Still failed. The capacity on the device is 250 GB. After the second attempt, the device is only 46 % full.

Output from df -h (truncated for brevity):

[foo@bar ~]$ df -h
File system          Size  Used Avail. Usage% Mount point
/dev/nvme0n1p4        49G   42G   5,2G    89% /
tmpfs                 16G   15G   598M    97% /tmp
/dev/nvme0n1p3       2,0G  403M   1,4G    22% /boot
/dev/nvme0n1p14      590G  511G    50G    92% /home
/dev/nvme0n1p1      1022M  6,3M  1016M     1% /boot/efi
tmpfs                3,2G  216K   3,2G     1% /run/user/1000
/dev/sda2            228G   99G   118G    46% /mnt/EXTERNAL     # <-- The external device

Question:

Why does makepkg fail? Does makepkg consume disk space on partitions apart from the one hosting the Build directory from which makepkg is invoked?

Last edited by SeagullFish (2025-05-25 09:54:58)

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,613

Re: [SOLVED] Disk space issues while trying to update electron32

I suspect you are running out of space on /tmp

mpan

Member

Registered: 2012-08-01

Posts: 1,422

Website

Re: [SOLVED] Disk space issues while trying to update electron32

Indeed, that “/tmp” looks morbidly full.

But, if that’s not it: what is the file system you use? How do you measure the free/used space (the exact command, the exact output)? What does `df -i` say for the affected file systems?

---

Sometimes I seem a bit harsh — don’t get offended too easily!

SeagullFish

Member

Registered: 2023-08-10

Posts: 53

Re: [SOLVED] Disk space issues while trying to update electron32

I suspect you are running out of space on /tmp

Indeed, that “/tmp” looks morbidly full. [...]

It seems that you were right. I tried circumventing the issue:

[foo@bar electron32]$ sudo mkdir /mnt/EXTERNAL/tmp
[foo@bar electron32]$ sudo mount --bind /mnt/EXTERNAL/tmp /tmp
[foo@bar electron32]$ makepkg -s

This solved the diskspace issue temporary while building. It should be noted, though, that if anyone else chooses to replicate this solution in other use cases, it is also important to do the following actions when done:

[foo@bar electron32]$ sudo umount /tmp
[foo@bar electron32]$ sudo rm -rf /mnt/EXTERNAL/tmp

However, I also encountered several other challenges that prevented me from building the package (according to ChatGPT: Rust allocation linking issues and LTO metadata mismatch in Rust .rlib files). After some research, I found that electron32 was originally installed to satisfy dependencies from another package, but that the other package no longer requires electron32. And no other packages requires electron32, so I decided to uninstall it.

Since the issue is no longer relevant, I am changing the status to [SOLVED].