unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: 38088-done@debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Thu, 7 Nov 2019 08:40:10 +0100	[thread overview]
Message-ID: <CAE4v=ph00fDkb8hauKNx5=ORdWva42Sb8=UgRSopqdWO9=zwLw@mail.gmail.com> (raw)
In-Reply-To: <87eeykqgti.fsf@roquette.mug.biscuolo.net>

It seems this was a filesystem corruption. Everything seems fine after reboot,
so closing.

Giovanni Biscuolo <g@xelera.eu> ezt írta (időpont: 2019. nov. 7., Cs, 8:36):
>
> Hello Gabor,
>
> Gábor Boskovits <boskovits@gmail.com> writes:
>
> [...]
>
> >> From the screenshot, it seems that your root file system (or at least
> >> /tmp and /gnu/store) became read-only, which in turn caused various
> >> things to fail, including guix-daemon (hence the “broken pipe” when
> >> ‘guix build’ was talking to it, I suppose.)
> >
> > Yes, it also became corrupted. fsck on boot fixed it.
> > Since then it works happily again...
>
> if the problem depended on filesystem corruption and all is fine now for
> you, could you also close this bug please?
>
> [...]
>
> Thanks! Gio'
>
> --
> Giovanni Biscuolo
>
> Xelera IT Infrastructures



-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

  reply	other threads:[~2019-11-07  7:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 14:15 bug#38088: Guix system becomes unresponsive after backtrace Gábor Boskovits
2019-11-06 15:52 ` Danny Milosavljevic
2019-11-06 22:42   ` Gábor Boskovits
2019-11-06 17:42 ` Ludovic Courtès
2019-11-06 22:40   ` Gábor Boskovits
2019-11-07  7:35     ` Giovanni Biscuolo
2019-11-07  7:40       ` Gábor Boskovits [this message]
2019-11-07 20:58     ` Ludovic Courtès

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='CAE4v=ph00fDkb8hauKNx5=ORdWva42Sb8=UgRSopqdWO9=zwLw@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=38088-done@debbugs.gnu.org \
    --cc=g@xelera.eu \
    /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).