From: "Gábor Boskovits" <boskovits@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 38088@debbugs.gnu.org
Subject: bug#38088: Guix system becomes unresponsive after backtrace
Date: Wed, 6 Nov 2019 23:42:30 +0100 [thread overview]
Message-ID: <CAE4v=pggGehgnh4o701DVJRic3hqqn7Oza7cKW7zdujWE+aWHw@mail.gmail.com> (raw)
In-Reply-To: <20191106165235.614a4d8a@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> ezt írta (időpont: 2019.
nov. 6., Sze, 16:52):
>
> 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.
I also believe it was the root filesystem.
>
> Could you check dmesg for signs?
I believe the dmesg info was lost on force-restart. Logs contain nothing....
Regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2019-11-06 22:43 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 [this message]
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='CAE4v=pggGehgnh4o701DVJRic3hqqn7Oza7cKW7zdujWE+aWHw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=38088@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
/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).