unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: error: build failed: committing transaction: disk I/O error
Date: Wed, 19 Mar 2014 02:52:02 -0400	[thread overview]
Message-ID: <87ob12r88d.fsf@yeeloong.lan> (raw)
In-Reply-To: <874n35ngbu.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 11 Mar 2014 12:08:05 +0100")

ludo@gnu.org (Ludovic Courtès) writes:

> Mark H Weaver <mhw@netris.org> skribis:
>
>> In recent weeks on my system, it has become fairly common for the daemon
>> to get into a bad state, where all build attempts fail with messages
>> like this:
>>
>> mhw:~/guix-core-updates$ ./pre-inst-env guix build -n emacs
>> error (ignored): aborting transaction: cannot rollback - no transaction is active
>> guix build: error: build failed: committing transaction: disk I/O error
>> mhw:~/guix-core-updates$ 
>
> (The message comes from SQLite.)

I looked into this further, and the problem is that sqlite is trying to
mmap a 32K page, but my kernel is configured for 64K pages, so the mmap
fails.

It appears that I'll need to apply a fix for sqlite, once I figure out
how to do so.  Unfortunately, it seems possible that the page size is
effectively part of the file format, and that fixing this would render
existing sqlite databases unreadable on MIPS.  I'm awaiting moderator
approval to subscribe to their mailing lists, and will consult with the
developers ASAP.

    Thanks,
      Mark

      reply	other threads:[~2014-03-19  6:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  4:20 error: build failed: committing transaction: disk I/O error Mark H Weaver
2014-03-11 11:08 ` Ludovic Courtès
2014-03-19  6:52   ` Mark H Weaver [this message]

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=87ob12r88d.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=guix-devel@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.
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).