From: zimoun <zimon.toutoune@gmail.com>
To: Peter Bhat Harkins <peter@push.cx>, 54453@debbugs.gnu.org
Subject: bug#54453: crash running 'guix pull'
Date: Tue, 22 Mar 2022 19:52:48 +0100 [thread overview]
Message-ID: <865yo5akfz.fsf@gmail.com> (raw)
In-Reply-To: <20220321212316.sdqc7le6slzkxbpj@push.cx>
Hi,
On Mon, 21 Mar 2022 at 16:23, Peter Bhat Harkins <peter@push.cx> wrote:
> The VPS was created almost two years ago, and 'guix pull' was run many
> times, though not in the last few months.
Did you garbage collect “guix gc”? For instance with the option ’-F 5G’
or this option ’-d 9m’.
Because if you pull again and again, the store is growing. And
depending on the size your VPS, you can reach the limit of the available
space.
> Is there documentation anywhere of what system resources a guix system,
> or this particular command, requires? Is there any method for
> estimating? It sounds like you're suggesting the requirements have
> changed over time. Do running guix systems require more disk and RAM as
> they age, or does this undocumented requirement also apply to new
> systems?
No, I am not suggesting a change. I am trying to identify why your
setup is failing and emit hypothesis.
> At this point I'm less concerned about this individual crash bug and
> more concerned that running any guix system is unsustainable.
You are drawing hard conclusions from some hypothesis when they are just
hypothesis.
Over this 2 years, how many times did you garbage collect?
Cheers,
simon
prev parent reply other threads:[~2022-03-22 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 18:56 bug#54453: crash running 'guix pull' Peter Bhat Harkins
2022-03-18 21:03 ` Maxime Devos
2022-03-18 22:13 ` Peter Bhat Harkins
2022-03-21 16:58 ` zimoun
2022-03-21 19:10 ` Peter Bhat Harkins
2022-03-21 19:36 ` zimoun
2022-03-21 21:23 ` Peter Bhat Harkins
2022-03-22 18:52 ` zimoun [this message]
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=865yo5akfz.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54453@debbugs.gnu.org \
--cc=peter@push.cx \
/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).