GNU bug report logs - #38088
Guix system becomes unresponsive after backtrace

Previous Next

Full log

View this message in rfc822 format

From: Danny Milosavljevic <dannym <at> scratchpost.org>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 16:52:35 +0100

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

Hi Gábor,

On Wed, 6 Nov 2019 15:15:41 +0100
Gábor Boskovits <boskovits <at> 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?

[Message part 2 (application/pgp-signature, inline)]

Previous Next

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