From: Nathan Dehnel <ncdehnel@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 45266@debbugs.gnu.org
Subject: bug#45266: "guix gc" needs free disk space to function
Date: Tue, 22 Dec 2020 12:05:04 -0600 [thread overview]
Message-ID: <CAEEhgEvkaOhpBmR_SWrZyLG2MH7NO0JrWzNFEak=FAuxb6JQ0g@mail.gmail.com> (raw)
In-Reply-To: <875z4t29g6.fsf@gnu.org>
>The daemon reserves a bit of extra space before starting operation (see
‘reserve-space?’ in (guix store)), which should be enough to gracefully
handle situations where builds are filling the disk.
>However, there can also be non-Guix processes filling the disk, to the
point where it’s completely full, and at that point sqlite3 (which the
daemon uses) may be unable to operate.
I didn't experience this. Guix pull filled the disk, which prevented
the gc from working. It's possible some other process was writing in
the background, but I had built an image which was almost completely
devoid of programs and services.
>I’m afraid there’s little we can do in this case.
>Thoughts?
Copy the database into tmpfs temporarily?
On Tue, Dec 22, 2020 at 8:37 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi,
>
> Nathan Dehnel <ncdehnel@gmail.com> skribis:
>
> > It would be better if guix gc could run on a disk that was completely
> > full, as right now it cannot be used to free space on a full disk.
>
> The daemon reserves a bit of extra space before starting operation (see
> ‘reserve-space?’ in (guix store)), which should be enough to gracefully
> handle situations where builds are filling the disk.
>
> However, there can also be non-Guix processes filling the disk, to the
> point where it’s completely full, and at that point sqlite3 (which the
> daemon uses) may be unable to operate.
>
> I’m afraid there’s little we can do in this case.
>
> Thoughts?
>
> Ludo’.
next prev parent reply other threads:[~2020-12-22 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 6:36 bug#45266: "guix gc" needs free disk space to function Nathan Dehnel
2020-12-22 14:37 ` Ludovic Courtès
2020-12-22 18:05 ` Nathan Dehnel [this message]
2021-03-12 4:56 ` Vincent Legoll
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='CAEEhgEvkaOhpBmR_SWrZyLG2MH7NO0JrWzNFEak=FAuxb6JQ0g@mail.gmail.com' \
--to=ncdehnel@gmail.com \
--cc=45266@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).