From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 44723@debbugs.gnu.org
Subject: bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502)
Date: Wed, 18 Nov 2020 21:13:55 +0100 [thread overview]
Message-ID: <20201118201355.GA2833@LionPure> (raw)
In-Reply-To: <CAJ3okZ3fawBARjyc+0q-hG468MooXEk2Gy5c38YG89VqErhM7A@mail.gmail.com>
Hi,
On +2020-11-18 18:50:03 +0100, zimoun wrote:
> Hi,
>
> On Wed, 18 Nov 2020 at 18:46, Ludovic Courtès <ludo@gnu.org> wrote:
>
> > I guess it’s OK for Guix System ISO images because a fresh one gets
> > built at each evaluation, roughly, but perhaps the Hurd images are not
> > rebuilt frequently enough and the changes that they’re GC’d are higher.
> >
> > I don’t have a good solution for that, we’re consuming storage space too
> > quickly with all these images currently. :-/
>
Eric Blake from Red Hat is IIUC working on qemu features to share clean parts
of images without duplicating [1] and LWN has an article re his work [2]
(I hope posting this [2] subsriberlink here is Ok with LWN -- I would think so)
Perhaps their incremental chaining technology can help consolidate "all these images" ?
> Does it make sense to only keep the latest? And GC all the older one
> except the stable one (pinned).
>
> Cheers,
> simon
>
>
>
[1] https://static.sched.com/hosted_files/kvmforum2020/92/kvmforum_2020_Bitmaps_and_NBD.pdf
[2] https://lwn.net/SubscriberLink/837053/06072931fc4162bf/
([2] should be available freely to all as [3] in less than a week)
[3] https://lwn.net/Articles/837053/
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2020-11-18 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 16:39 bug#44723: Latest binary tarball & Hurd qcow2 image unavailable (502) Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-18 17:45 ` Ludovic Courtès
2020-11-18 17:50 ` zimoun
2020-11-18 19:16 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-18 20:13 ` Bengt Richter [this message]
2020-11-19 8:05 ` Ludovic Courtès
2020-11-19 8:43 ` zimoun
2020-11-19 9:14 ` Mathieu Othacehe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201118201355.GA2833@LionPure \
--to=bokr@bokr.com \
--cc=44723@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).