unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: vikram sai balaji ulaganathan <tayirvadai.vikram@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Guix pull issue
Date: Sat, 01 Sep 2018 16:52:43 +0200	[thread overview]
Message-ID: <87k1o5cls4.fsf@gnu.org> (raw)
In-Reply-To: <CAL=8aa-6DZvBshdqcryO-T-OyEEaEMci4oq6pmo=4j9=g1S9Fg@mail.gmail.com> (vikram sai balaji ulaganathan's message of "Thu, 30 Aug 2018 01:11:41 -0400")

Hello,

vikram sai balaji ulaganathan <tayirvadai.vikram@gmail.com> skribis:

> For a few weeks now, I have been trying to get guix pull to update
> everything but get the below error. Guix is at .15.0

What does “uname -srvm” return on this machine?

> In guix/serialization.scm:
>    371:23  3 (_ "bash")
>    357:13  2 (dump _)
>     225:6  1 (write-contents-from-port #<input: gnu/packages/bootst…> …)
> In unknown file:
>            0 (sendfile #<input-output: file 10> #<input: gnu/packag…> …)
>
> ERROR: In procedure sendfile:
> In procedure sendfile: Input/output error

Guix internally relies on the sendfile(2) system call to efficiently
communicate with the build daemon.  Here, it could be that the storage
device where those files are is dysfunctional, or that the file system
is corrupt, or that something is wrong with the kernel.

Does “dmesg | tail” show any useful hint when invoked right after the
error?

Thanks,
Ludo’.

  reply	other threads:[~2018-09-01 14:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  5:11 Guix pull issue vikram sai balaji ulaganathan
2018-09-01 14:52 ` Ludovic Courtès [this message]
2018-09-01 15:41   ` vikram sai balaji ulaganathan
2018-09-04  0:01   ` vikram sai balaji ulaganathan
2018-09-04  4:25     ` vikram sai balaji ulaganathan
2018-09-04  8:21       ` Ricardo Wurmus

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=87k1o5cls4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=tayirvadai.vikram@gmail.com \
    /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. 
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).