From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: error: build failed: committing transaction: disk I/O error Date: Wed, 19 Mar 2014 02:52:02 -0400 Message-ID: <87ob12r88d.fsf@yeeloong.lan> References: <8761nlicxo.fsf@yeeloong.lan> <874n35ngbu.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60365) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WQAMl-0001Lh-E8 for guix-devel@gnu.org; Wed, 19 Mar 2014 02:52:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WQAMg-000417-4G for guix-devel@gnu.org; Wed, 19 Mar 2014 02:52:43 -0400 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") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > Mark H Weaver 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$=20 > > (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