https://sourceware.org/bugzilla/show_bug.cgi?id=27399
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fche at redhat dot com
Status|NEW |WAITING
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Can you check whether dpkg-deb is decompressing all of its content onto some
RAM-backed filesystem, and running out of space via that (or via consuming
machine free ram)?
You can try a few things:
- run debuginfod with a smaller concurrency limit (-c NNN), because the
decompression etc. activities aggressively use all your CPUs and thus
#CPU * memory, if they can
- instead of 'debuginfod -U' (which uses dpkg-deb as the decompression
streamer), use
% debuginfod -Z.deb="(bsdtar -O -x -f - data.tar.xz)<"
which causes deb files to be processed with libarchive's frontend
(or equivalently, temporarily rename /usr/bin/dpkg-deb while starting
debuginfod, so it makes the same inference)
- monitor resource usage - particularly ram - during the indexing process
- try running elfutils 0.183 debuginfod, which does a touch more
filesystem-space monitoring, related self-protection, more
prometheus error metrics
--
You are receiving this mail because:
You are on the CC list for the bug.
