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

Previous Next

Full log

Message #20 received at 38088 <at> debbugs.gnu.org (full text, mbox):

From: Giovanni Biscuolo <g <at> xelera.eu>
To: Gábor Boskovits <boskovits <at> gmail.com>
Cc: 38088 <at> debbugs.gnu.org
Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace
Date: Thu, 07 Nov 2019 08:35:53 +0100

Hello Gabor,

Gábor Boskovits <boskovits <at> 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

Previous Next

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