unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: 57583@debbugs.gnu.org, yusuftalha@tuta.io
Subject: bug#57583: Guix cannot resume after hibernation
Date: Mon, 05 Sep 2022 14:38:25 +0200	[thread overview]
Message-ID: <871qsqgexl.fsf@nckx> (raw)
In-Reply-To: <87bkrvawgp.fsf@jpoiret.xyz>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

Hi again,

Josselin Poiret via Bug reports for GNU Guix 写道：
>                    (and testing these kinds of features is 
>                    dangerous,
> you could make a wrong move and incur heavy data loss)

I couldn't agree moEXT4-fs ext4_get_branch:171: inode #8: block 
30343695: comm jbd2/sdb7-8: invalid block
Aborting journal on device sdb7-8.

…ya know, I actually wrote a patch that I thought I'd submitted, 
but apparently not?  Or I'm failing to use Mumi again.

We should scan all swap areas for the S1SUSPEND signature, and do 
a much better thing than the current behaviour if we find one.

I'll see if I can find it in a backup somewhEXT4-fs (sdb7): 
Remounting filesystem read-only

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  reply	other threads:[~2022-09-05 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 16:37 bug#57583: Guix cannot resume after hibernation Yusuf Talha via Bug reports for GNU Guix
2022-09-04 17:19 ` Josselin Poiret via Bug reports for GNU Guix
2022-09-05 12:38   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-09-05 12:51   ` Ludovic Courtès
2022-09-05 13:05     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-12-10  1:11       ` Mekeor Melire
2022-09-05 12:13 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-09-06  2:23 ` bug#57583: Yusuf Talha via Bug reports for GNU Guix

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=871qsqgexl.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=57583@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=me@tobias.gr \
    --cc=yusuftalha@tuta.io \
    /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).