unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 38088@debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 16:52:35 +0100	[thread overview]
Message-ID: <20191106165235.614a4d8a@scratchpost.org> (raw)
In-Reply-To: <CAE4v=pib7J-rrcR9JDXN8iLdy2bMtUK+b7kPVMH4No35doRcGw@mail.gmail.com>

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

Hi Gábor,

On Wed, 6 Nov 2019 15:15:41 +0100
Gábor Boskovits <boskovits@gmail.com> wrote:

> This happened when I was trying a pre-inst-env guix build from a
> core-updates checkout.
> Previously python3 failed to build, and I was trying to build it again.

Hmm, sounds like disk corruption.  If there's a sudden read-only appearing then
it's often because the kernel found a file system error and doesn't want to make
the situation worse.  It then remounts the affected file-system read-only.
According to the top of your screenshot, even /tmp is read-only.  I think we
don't use a tmpfs, so that's the root file system.

Could you check dmesg for signs?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-11-06 15:53 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 [this message]
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
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=20191106165235.614a4d8a@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=38088@debbugs.gnu.org \
    --cc=boskovits@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).