From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Subject: bug#34281: guix pull - maybe a bug
Date: Mon, 04 Feb 2019 22:30:06 +0100
Message-ID: <87bm3rp7hd.fsf@gnu.org>
References: <CALwiZw5ZfGZNDdxQSHhj+j2G5mVMDwTv-3tMn3Pq+6j3TCuBUg@mail.gmail.com>
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 ([209.51.188.92]:51031)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gqlpZ-0006vY-TQ
	for bug-guix@gnu.org; Mon, 04 Feb 2019 16:31:06 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gqlpX-0002Gs-W4
	for bug-guix@gnu.org; Mon, 04 Feb 2019 16:31:05 -0500
Received: from debbugs.gnu.org ([209.51.188.43]:60493)
	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 1gqlpW-0002Fs-H5
	for bug-guix@gnu.org; Mon, 04 Feb 2019 16:31:03 -0500
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gqlpW-0000Rk-CW
	for bug-guix@gnu.org; Mon, 04 Feb 2019 16:31:02 -0500
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.34281.B34281.15493158111649@debbugs.gnu.org>
In-Reply-To: <CALwiZw5ZfGZNDdxQSHhj+j2G5mVMDwTv-3tMn3Pq+6j3TCuBUg@mail.gmail.com>
	(Thibaut Brandscheid's message of "Fri, 1 Feb 2019 21:14:08 +0100")
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: Thibaut Brandscheid <randaltor@web.de>
Cc: 34281@debbugs.gnu.org

Hello,

Thibaut Brandscheid <randaltor@web.de> skribis:

> I use openSUSE Tumbleweed and got n the last days a faulty update. This
> happens maybe ones or twice a year. So I did what I always do, I revert t=
he
> non-user file system to an older btrfs snapshot. The thing is, that guix
> pull does no longer work after the system rollback.

[...]

> ./guix/store.scm:982:9: Throw to key `srfi-34' with args `(#<condition &s=
tore-protocol-error [message: "opening file `/gnu/store/vncqqf1nzbbc4hkaib5=
mkpzr4vn61qdl-guile-git-0.2.0.drv': No such file or directory" status: 1] 5=
549720>)'.

By reverting to an earlier Btrfs snapshot, you ended up with a corrupt
store.  The store actually consists of two things: the files under
/gnu/store, and the /var/guix/db/db.sqlite database that contains
metadata about those files.  Presumably, after you reverted to an
earlier snapshot, those two bits got out of sync, leading to the error
above.

At this point you may have to reinstall Guix.  The take-away is that you
should never rely on file-system-level rollbacks for Guix; instead use
the mechanisms that Guix provides, such as =E2=80=98--roll-back=E2=80=99.

Thanks,
Ludo=E2=80=99.