From: vikram sai balaji ulaganathan <tayirvadai.vikram@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Guix pull issue
Date: Mon, 3 Sep 2018 20:01:17 -0400 [thread overview]
Message-ID: <CAL=8aa-R_zOqpJY39jfejLBvr2ahVqfmC3XPPRgM-K-o4xqG9g@mail.gmail.com> (raw)
In-Reply-To: <87k1o5cls4.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
Uname shows Linux 4.17.13-gnu #1 SMP 1x86_64
dmesg is not revealing anything. dmesg is not updating for this operation
Is there another command that needs to be run or do I have restart guix
daemon.
Thanks
Vikram
On Sat, Sep 1, 2018, 10:57 AM Ludovic Courtès <ludo@gnu.org> wrote:
> 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’.
>
[-- Attachment #2: Type: text/html, Size: 1926 bytes --]
next prev parent reply other threads:[~2018-09-04 0:01 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
2018-09-01 15:41 ` vikram sai balaji ulaganathan
2018-09-04 0:01 ` vikram sai balaji ulaganathan [this message]
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='CAL=8aa-R_zOqpJY39jfejLBvr2ahVqfmC3XPPRgM-K-o4xqG9g@mail.gmail.com' \
--to=tayirvadai.vikram@gmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@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.
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).