GNU bug report logs - #34281
guix pull - maybe a bug

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34281 in the body.
You can then email your comments to 34281 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Thibaut Brandscheid <randaltor <at> web.de>
To: bug-guix <at> gnu.org
Subject: guix pull - maybe a bug
Date: Fri, 1 Feb 2019 21:14:08 +0100

[Message part 1 (text/plain, inline)]

Hi,

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 the
non-user file system to an older btrfs snapshot. The thing is, that guix
pull does no longer work after the system rollback.
Since this kind of problem might be new to Guix, I decided to write you an
email.

I guess my local profile has some soft-links to non-existing folders or
files.
Any hint on how to resolve this?

If you need more info, I'm glad to help.

Greetings
Thibaut

[Message part 2 (text/html, inline)]

[guix_pull_output.txt (text/plain, attachment)]

Message #8 received at 34281 <at> debbugs.gnu.org (full text, mbox):

From: Ludovic Courtès <ludo <at> gnu.org>
To: Thibaut Brandscheid <randaltor <at> web.de>
Cc: 34281 <at> debbugs.gnu.org
Subject: Re: bug#34281: guix pull - maybe a bug
Date: Mon, 04 Feb 2019 22:30:06 +0100

Hello,

Thibaut Brandscheid <randaltor <at> 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 the
> 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 &store-protocol-error [message: "opening file `/gnu/store/vncqqf1nzbbc4hkaib5mkpzr4vn61qdl-guile-git-0.2.0.drv': No such file or directory" status: 1] 5549720>)'.

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 ‘--roll-back’.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.