From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#31843: guix pull corrupted current guix
Date: Fri, 15 Jun 2018 17:27:16 +0200
Message-ID: <87tvq4rrxn.fsf@gnu.org>
References: <599124aabcd5140179562c358198ecd1@lepiller.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:51383)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fTqdv-0005rK-AP
	for bug-guix@gnu.org; Fri, 15 Jun 2018 11:28:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fTqdu-00085i-Fp
	for bug-guix@gnu.org; Fri, 15 Jun 2018 11:28:03 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:42663)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1fTqdu-00085c-AF
	for bug-guix@gnu.org; Fri, 15 Jun 2018 11:28:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1fTqdu-0001ck-1K
	for bug-guix@gnu.org; Fri, 15 Jun 2018 11:28:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.31843.B31843.15290764466198@debbugs.gnu.org>
In-Reply-To: <599124aabcd5140179562c358198ecd1@lepiller.eu> (Julien Lepiller's
	message of "Fri, 15 Jun 2018 13:25:43 +0200")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 31843@debbugs.gnu.org

Hello,

Julien Lepiller <julien@lepiller.eu> skribis:

> Hi, running guix pull this morning corrupted my current guix command.

Let=E2=80=99s not jump to the conclusion.  :-)

> I am running on guixsd. Because I don't have a lot of memory, I sent a
> generation of .config/guix/current to the server with:
>
> guix archive --export -r `readlink -f .config/guix/current` | ssh
> machine guix archive --import

Note that you can use =E2=80=98guix copy=E2=80=99 instead, which avoids sen=
ding store
items already present on the target.

> This morning, I tried to run guix pull to see how far it would go (and
> if I could download some parts from hydra or berlin). As expected, it
> ran out of memory, but left my store in a state where the guix command
> linked to from .config/guix/current only contains garbage. Attached is
> the output of "guix pull --cores=3D1" on that machine that lead to the
> bug, and the new content of the guix command.
>
> The corrupted file is from a store item that was present (and valid)
> before I ran guix pull, so I thought it was impossible for guix to
> modify it.

[...]

> compiling...	100.0% of 1 files
> compiling...	 65.0% of 40 filesIn ice-9/boot-9.scm:
>     829:9 19 guile: symbol lookup error: /gnu/store/6mfd4f8gy11rgn2xk00cn=
slmrslg9w7h-guile-2.2.3/lib/libguile-2.2.so.1: undefined symbol: u8_mbtoucr
> guix pull: error: corrupt input while restoring archive from #<closed: fi=
le 31742a0>

To me, this error suggests that
/gnu/store/6mfd4f8gy11rgn2xk00cnslmrslg9w7h-guile-2.2.3 was already
corrupt at the time you run =E2=80=98guix pull=E2=80=99.

Did you try running =E2=80=98guix gc --verify=E2=80=99 on that machine (usi=
ng an older
Guix)?

Are there signs in the kernel log of a file system corruption?

Thanks,
Ludo=E2=80=99.