unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: noloader@gmail.com, 53000@debbugs.gnu.org
Subject: bug#53000: How to reclaim space when no space is available?
Date: Tue, 04 Jan 2022 07:56:01 +0100	[thread overview]
Message-ID: <20431b5808c892bcb2fa27b3091d489741b7e369.camel@ist.tugraz.at> (raw)
In-Reply-To: <CAH8yC8mnQMO0D8Rv-zge+JY8Cbe5a73jhYrtcQ5MW7B4qnctgQ@mail.gmail.com>

Am Montag, dem 03.01.2022 um 23:12 -0500 schrieb Jeffrey Walton:
> Hi Everyone,
> 
> I've run out of disk space. I'm trying to run 'guix gc' but it seems
> to need disk space to perform the garbage collection.
> 
> $ sudo guix gc
I don't think the manuals specify using `sudo guix gc'.  Last time I
checked a normal `guix gc' does the same, as the logic is in either way
handed off to the daemon running as root already.

> finding garbage collector roots...
> note: can't create trash directory: creating directory
> `/gnu/store/trash': No space left on device
> deleting garbage...
> ...
> error (ignored): aborting transaction: cannot rollback - no
> transaction is active guix gc: error: committing transaction:
> database or disk is full
> 
> Does anyone know how to delete all old packages and artifacts without
> the need for some free disk space?
It's a known bug that you currently can't free space without having
space.  (You can try searching for similar bug IDs or you can wait for
someone else to link you to them.)  The "fix" would ironically be to
sacrifice even more space to Guix by avoiding store deduplication,
because then store items can easily be deleted.

You could try manually freeing up space, but as someone who already
messed with GC internals I'd heavily suggest you avoid doing that. 
Unless you don't mind stuffing kittens in a blender, that is.

> I don't need old stuff. I use the VM to test builds and run self
> tests of some packages I am responsible for. I don't need the extra
> bells and whistles.
Those extra bells and whistles are the entire point of functional
package management.  You get backups and roll-backs for free.  If you
think VMs or Docker containers are sufficient for testing purposes
while you happily accept Debian overwriting files in-place, that is a
position you can hold, but it is not the Nix/Guix way.

Cheers




  reply	other threads:[~2022-01-04  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04  4:12 bug#53000: How to reclaim space when no space is available? Jeffrey Walton
2022-01-04  6:56 ` Liliana Marie Prikler [this message]
2022-01-04 10:00 ` Mark H Weaver
2022-01-04 17:30   ` Leo Famulari

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=20431b5808c892bcb2fa27b3091d489741b7e369.camel@ist.tugraz.at \
    --to=liliana.prikler@ist.tugraz.at \
    --cc=53000@debbugs.gnu.org \
    --cc=noloader@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).