all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: 52919@debbugs.gnu.org
Subject: bug#52919: Hidden "disk-image-rw" files aren't deleted after use, filling $tmpdir
Date: Mon, 03 Jan 2022 15:56:54 +0100	[thread overview]
Message-ID: <87pmp850ll.fsf@gnu.org> (raw)
In-Reply-To: <Yc9JbdUxDKHKHPtt@jasmine.lan> (Leo Famulari's message of "Fri, 31 Dec 2021 13:18:21 -0500")


Hello Leo,

> This is new. I think the issue was introduced with recent work on (gnu
> system image), perhaps from this commit:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=da924796744bbb7b035a986fe5d28d8d613ff6af

Before that commit "guix system vm" was always producing volatile
images, regardless of the "--volatile" argument. The new behaviour is to
only produce volatile images if "--volatile" is passed.

This means that by default, "disk-image-rw" are created in /tmp so that
QEMU can operate on RW images. The side effect is that those big images
can fill /tmp pretty quickly as you noticed.

We could use the ~/.cache/guix directory instead to store those
images. We could also make "--volatile" the default and introduce a
"--persistent" argument instead. That would restore the previous "guix
system vm" behaviour.

WDYT?

Thanks,

Mathieu





  reply	other threads:[~2022-01-03 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-31 18:18 bug#52919: Hidden "disk-image-rw" files aren't deleted after use, filling $tmpdir Leo Famulari
2022-01-03 14:56 ` Mathieu Othacehe [this message]
2022-01-04  8:17   ` Ludovic Courtès
2022-01-04 17:26     ` Leo Famulari
2022-01-11 12:33       ` Mathieu Othacehe
2022-01-12 20:54         ` Ludovic Courtès
2022-01-13 10:55           ` Mathieu Othacehe
2022-01-13 14:49             ` Ludovic Courtès
2022-01-14 11:27               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmp850ll.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=52919@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.