all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: HiPhish <hiphish@posteo.de>
To: help-guix@gnu.org
Subject: Borg takes forever to upgrade
Date: Thu, 14 Mar 2019 21:12:58 +0100	[thread overview]
Message-ID: <3878643.TA5XZMSakg@aleksandar-ixtreme-m5740> (raw)

Hello everyone,

I was trying to upgrade my packages and Borg (the backup program) has been
taking over an hour already. I have eventually decided to cancel the upgrade
process and tried upgrading all packages except Borg. The upgrade process
finished without problems in a reasonable amount of time, so it is definitely
Borg where things get stuck.

I'm running Guix version 8cc3983a4d02a15ad4a863671c1a5a8b2b542625 after
having run `guix pull` today. Here is the output of top:

    $ top -u guixbuilder01

    top - 21:11:24 up  8:53,  4 users,  load average: 1.24, 1.54, 1.36
    Tasks: 252 total,   2 running, 189 sleeping,   0 stopped,   0 zombie
    %Cpu(s): 30.3 us,  4.4 sy,  0.0 ni, 63.0 id,  2.1 wa,  0.0 hi,  0.2 si,  0.0 st
    KiB Mem :  6094692 total,   324704 free,  3076416 used,  2693572 buff/cache
    KiB Swap:  2097148 total,  2088176 free,     8972 used.  2595796 avail Mem 

      PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                      
    28132 guixbui+  20   0  272972 264756  12804 R 100.0  4.3 118:56.74 .py.test-real                                                
     4312 guixbui+  20   0   49068  29268  11508 S   0.0  0.5   0:00.61 python                                                       
    27994 guixbui+  20   0  132792  18296   9452 S   0.0  0.3   0:00.18 guile

Does anyone have an idea of what is going on here?

             reply	other threads:[~2019-03-14 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14 20:12 HiPhish [this message]
2019-03-14 20:31 ` Borg takes forever to upgrade Leo Famulari
2019-03-14 22:09   ` HiPhish
2019-04-22 21:19     ` Christopher Lemmer Webber
2019-03-14 20:39 ` Tobias Geerinckx-Rice
2019-03-14 22:15   ` HiPhish

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=3878643.TA5XZMSakg@aleksandar-ixtreme-m5740 \
    --to=hiphish@posteo.de \
    --cc=help-guix@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 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.