all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Ekaitz Zarraga <ekaitz@elenq.tech>, 53696@debbugs.gnu.org
Subject: bug#53696: Integer overflow on Guix GC size calculation
Date: Wed, 02 Feb 2022 11:05:31 +0100	[thread overview]
Message-ID: <f0a7920cbd0c80894a305e535031f1e1bb4403e2.camel@telenet.be> (raw)
In-Reply-To: <ZbUG0J0t7mjKPrXaPwoPrhN-Qx-jMae7vM2CCoOV-kHm7ID85ZoiNij86PcR8_zB2O9-DyxIPwWNlvCTS8AYSYemIuGJ4L8nNYwK0AXYuvQ=@elenq.tech>

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

Ekaitz Zarraga schreef op di 01-02-2022 om 14:06 [+0000]:
> [17592186042897 MiB] deleting '/gnu/store/wbz6vkiz7cq8c531xvb31lxm28nz332i-ghc-8.10.7'

For comparison, this is about 16 exbibyte.
According to <https://en.wikipedia.org/wiki/Byte#Multiple-byte_units>,
that's more than the global monthly Internet traffic in 2004.

According to <https://what-if.xkcd.com/31/>, 16 exbibyte would be about
17 million solid-state disks.  Even though this ignores deduplication,
this seems rather expensive. 

My guess is that the size of a store item was misrecorded somewhere.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-02-02 10:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 14:06 bug#53696: Integer overflow on Guix GC size calculation Ekaitz Zarraga
2022-02-01 21:20 ` Liliana Marie Prikler
2022-02-01 21:54   ` Ekaitz Zarraga
2022-02-02 19:45     ` Liliana Marie Prikler
2022-02-02 19:51       ` Ekaitz Zarraga
2022-02-02 20:04         ` Liliana Marie Prikler
2022-02-02 10:05 ` Maxime Devos [this message]
2022-02-02 12:04   ` Bengt Richter
2022-02-02 22:46     ` Bengt Richter
2022-02-08 10:01     ` Ludovic Courtès
2022-02-08 10:52       ` Ekaitz Zarraga
2022-02-10 20:25         ` Ludovic Courtès
2022-02-10 20:27           ` Ekaitz Zarraga

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=f0a7920cbd0c80894a305e535031f1e1bb4403e2.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=53696@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.