From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: 23666@debbugs.gnu.org
Subject: bug#23666: guix download fails for large files
Date: Wed, 01 Jun 2016 14:39:54 +0200 [thread overview]
Message-ID: <878typkrqd.fsf@gnu.org> (raw)
In-Reply-To: <20160531195631.GA22897@solar> (Andreas Enge's message of "Tue, 31 May 2016 21:56:31 +0200")
Andreas Enge <andreas@enge.fr> skribis:
> On my Novena with a 32 bit processor and 4 GB of main memory, this fails with
> guix download: error: sendfile: Broken pipe
>
> The file itself has 1,8 GB.
This is implemented using the ‘add-to-store’ RPC, which, after all these
years, is still implemented like this (nix/libstore/local-store.cc):
--8<---------------cut here---------------start------------->8---
Path LocalStore::addToStore(const string & name, const Path & _srcPath,
bool recursive, HashType hashAlgo, PathFilter & filter, bool repair)
{
Path srcPath(absPath(_srcPath));
debug(format("adding `%1%' to the store") % srcPath);
/* Read the whole path into memory. This is not a very scalable
method for very large paths, but `copyPath' is mainly used for
small files. */
--8<---------------cut here---------------end--------------->8---
This is undoubtedly what’s causing the failure.
Until this is fixed, you could wrap the file in a nar and import the nar
(nar import does not have this limitation, see ’LocalStore::importPath’
and co.).
To do that, you could do:
guix archive --export $(guix build -S texlive-texmf-whatever) > t.nar
and later:
guix archive --import < t.nar
HTH,
Ludo’.
next prev parent reply other threads:[~2016-06-01 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 19:56 bug#23666: guix download fails for large files Andreas Enge
2016-05-31 20:26 ` Leo Famulari
2016-06-01 12:39 ` Ludovic Courtès [this message]
2016-06-05 20:58 ` Andreas Enge
2016-06-06 7:06 ` 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
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=878typkrqd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23666@debbugs.gnu.org \
--cc=andreas@enge.fr \
/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).