all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Benjamin Slade <beoram@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: help-guix@gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: Re: Guix on aarch64
Date: Mon, 20 Aug 2018 21:52:24 -0600	[thread overview]
Message-ID: <87sh38ml53.fsf@jnanam.net> (raw)
In-Reply-To: <87va859baf.fsf@netris.org>

On 2018-08-20T11:51:20-0600, Mark H Weaver <mhw@netris.org> wrote:
 > I looked in the GNU tar source code to see what could produce that
 > message during archive creation.  The message would seem to indicate
 > that an error occurred during a kernel-level 'write' call to the archive
 > file.  The code is written to retry in case of short writes or EINTR.

 > What kind of filesystems are running on /tmp and /gnu?  How much free
 > space is on those filesystems?

/tmp is a tmpfs filesystem on ext4, and /gnu is on ext4. there was over
20Gb of free space.

I seemed to need to:

1) create a very large /tmp
2) create an even 2nd larger swapfile
3) increase swappiness to 100 (to make sure it actually used the
swapfile(s) before deciding it was out of memory)

Because one of the things it wanted to do (for tar?) was create a ">8Gb
sparse file", and this would fail with an "out of memory error" with the
a second 8Gb swapfile on top of my original 3Gb swapfile.

(Unfortunately, even after I fixed that, it chugged away for over
24hours, when I just wanted to install `emacs` and `certbot`. In the end
I just ended up using Nix to install these. :( ) 


--
Benjamin Slade - https://babbagefiles.xyz
  `(pgp_fp: ,(21BA 2AE1 28F6 DF36 110A 0E9C A320 BBE8 2B52 EE19))
    '(sent by mu4e on Emacs running under GNU/Linux . https://gnu.org )
       `(Choose Linux ,(Choose Freedom) . https://linux.com )

  reply	other threads:[~2018-08-21  3:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 15:27 Guix on aarch64 Benjamin Slade
2018-08-16 16:50 ` Clément Lassieur
2018-08-16 17:33   ` Benjamin Slade
2018-08-16 17:41   ` Benjamin Slade
2018-08-20 17:51     ` Mark H Weaver
2018-08-21  3:52       ` Benjamin Slade [this message]
2018-08-21  4:38         ` Leo Famulari
2018-08-21  5:20           ` Benjamin Slade
2018-08-21 17:44             ` Mark H Weaver
2018-08-21 21:31               ` Benjamin Slade
2018-08-23  4:58     ` Mark H Weaver
2018-08-23 16:09       ` Benjamin Slade
2018-08-24 10:32       ` Ludovic Courtès
2018-08-24 19:18         ` Ricardo Wurmus
2018-08-26 16:13         ` Mark H Weaver
2018-08-26 18:59           ` Leo Famulari
2018-08-27  8:04             ` Ricardo Wurmus
2018-08-27 18:54               ` Mark H Weaver
2018-08-27 19:11               ` Mark H Weaver
2018-08-27 19:26                 ` Ricardo Wurmus
2018-08-27 21:05                   ` Mark H Weaver
2018-08-27 21:56                     ` Mark H Weaver
2018-08-28  5:39                     ` Mark H Weaver
2018-08-28  7:57                     ` Ricardo Wurmus
2018-08-28 10:00                       ` Andreas Enge
2018-08-28 15:40                         ` Mark H Weaver
2018-08-28 19:09                       ` Leo Famulari
2018-08-28 19:22                         ` Mark H Weaver
2018-08-27 19:50               ` Leo Famulari
2018-08-27 20:37                 ` Ricardo Wurmus
2018-08-29 20:52               ` Joshua Branson
2018-08-30 20:47                 ` Ricardo Wurmus
2018-08-30  9:49           ` Ludovic Courtès

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=87sh38ml53.fsf@jnanam.net \
    --to=beoram@gmail.com \
    --cc=clement@lassieur.org \
    --cc=help-guix@gnu.org \
    --cc=mhw@netris.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.