From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27399] dpkg-deb/lzma error when indexing .debs
Date: Fri, 12 Feb 2021 11:28:43 +0000 [thread overview]
Message-ID: <bug-27399-10460-4nRKcXXW4p@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27399-10460@http.sourceware.org/bugzilla/>
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.
next prev parent reply other threads:[~2021-02-12 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 5:46 [Bug debuginfod/27399] New: " sergiodj at sergiodj dot net
2021-02-12 11:28 ` fche at redhat dot com [this message]
2021-02-12 13:09 ` [Bug debuginfod/27399] " fche at redhat dot com
2021-02-12 19:51 ` sergiodj at sergiodj dot net
2021-02-12 19:52 ` sergiodj at sergiodj dot net
2021-02-12 21:23 ` sergiodj at sergiodj dot net
2021-02-13 2:16 ` fche at redhat dot com
2021-02-13 18:13 ` sergiodj at sergiodj dot net
2021-03-02 21:54 ` fche at redhat dot com
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=bug-27399-10460-4nRKcXXW4p@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).