[minicoredumper] [External] [External] Debugging corrupt tar files (invalid sparse archive member)

[Jos Hulzink (Ellips B.V.)]

> Looking at your core file, it appears as though this may be from an application whose virtual address space is larger than 8GB. See a recently known issue about this:

> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_diamon_minicoredumper_issues_6&d=DwICAQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=5N90rj6avleIhhFOAVczeXUO76NE29a_GTjIG_9KNVQ&m=QRpDcUlCKsD41Fj2PKPp6a-1p-OfKYk7zW2Y800WrNg&s=e0mnCL2-L5QICuITU-OgLp_FUdFjBkV0FVMXjkGfmVU&e=



John,



Thanks for your investigation. Happy that we now at least have a clear where  the issue comes from. Our application processes up to a few thousand live camera images per second and can easily claim over 60 GB of memory... Let's just say we have good reasons why we would like to use minicoredumper 😊



Unfortunately, your proposed solution to dump directly into gzip is not an option for us, since we have to send the core dumps from sites like rural Africa/Australia over connections with less than desired upstream bandwidth. We know that gzip will have a tough time compressing our memory data, and the slow compression process will cause longer downtime of the system.



Best regards,



Jos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linutronix.de/pipermail/minicoredumper/attachments/20230209/709d25f7/attachment.htm>