From: bokr@bokr.com
To: zimoun <zimon.toutoune@gmail.com>
Cc: 59598@debbugs.gnu.org, Tyler Wolf <tyler@twolf.io>
Subject: bug#59598: "Unsupported manifest format" error
Date: Mon, 28 Nov 2022 00:34:43 +0100 [thread overview]
Message-ID: <20221127233443.GA3070@LionPure> (raw)
In-Reply-To: <86bkos1ta9.fsf@gmail.com>
Hi zimoun,
On +2022-11-27 13:22:22 +0100, zimoun wrote:
[...]
>
> This file lives in the store. Hum, I am surprised that a power shutdown
> removed this file.
>
Are all the conditions for a clean sync
of the file system where /gnu/store is mounted guaranteed?
What is the difference between power shutdown when you let
the battery run down and the OS shuts everything down
vs if you log out and click power down?
Is it not possible that when you have recharged the battery
and boot up that a journaling file system will discover traces
of an incomplete transaction (i.e. the one that was supposed
to record and atomically commit the missing file) and discards
it to reestabllish coherent file system state?
And what about continuations that were possibly waiting for
availability of that file?
Hopefully the OS will recover a good state, but what can
userland innocents expect to be guaranteed, in terms of
work flow they can understand?
(those with the grok-fu to understand internals won't need
much to imagine failure scenarios, but will presumably
appreciate /design/rationale/implementation/ documentation tips)
> Well, I do not know if you can recover this empty file. At least, you
> can the previous generation; e.g., guix package --roll-back.
>
Assuming the file system recovered -- a pretty good bet, but ... :)
> Or you can extract a previous manifest with,
>
> guix package -p /var/guix/profiles/per-user/<USER>/guix-profile-<NUMBER>-link \
> --export-manifest > /tmp/manifest-<NUMBER>.scm
>
> where <USER> and <NUMBER> depends on. Then,
>
> guix package -m /tmp/manifest-<NUMBER>scm
>
> will reinstall the same list of packages but at their current version
> (the ones of current Guix revision; guix describe).
>
>
> Cheers,
> simon
>
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2022-11-27 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 22:06 bug#59598: "Unsupported manifest format" error Tyler Wolf via Bug reports for GNU Guix
2022-11-27 12:22 ` zimoun
2022-11-27 23:34 ` bokr [this message]
2022-11-28 9:41 ` zimoun
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=20221127233443.GA3070@LionPure \
--to=bokr@bokr.com \
--cc=59598@debbugs.gnu.org \
--cc=tyler@twolf.io \
--cc=zimon.toutoune@gmail.com \
/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).