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: Sat, 13 Feb 2021 02:16:02 +0000 [thread overview]
Message-ID: <bug-27399-10460-hxXpsIiQHn@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27399-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27399
--- Comment #6 from Frank Ch. Eigler <fche at redhat dot com> ---
OK, my best guess is a transient low-memory condition. Just today we found bug
#27405, which can cause some impressive momentary memory binges in elfutils.
Reducing concurrency is one way to limit its impact, as you found. Giving the
VM more memory is another: I run it on 16GB 8CPU class VMs, scanning even many
huge debuginfo files, without a complaint.
It might also help reassure here is that if you let debuginfod keep going,
it'll know that it didn't finish indexing those problematic files, and will
just retry later. In the long term (past rescan time), such momentary ENOMEMs
are not particularly harmful.
I can't think of any debuginfod per se changes or bugs in effect here. Maybe
scale the default concurrency more conservatively to machine RAM rather than
solely CPU count?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-13 2:16 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 ` [Bug debuginfod/27399] " fche at redhat dot com
2021-02-12 13:09 ` 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 [this message]
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-hxXpsIiQHn@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).