From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#38088: Guix system becomes unresponsive after backtrace Date: Thu, 07 Nov 2019 21:58:06 +0100 Message-ID: <87tv7fmmjl.fsf@gnu.org> References: <87y2wsvr3m.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57955) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSorv-0001nS-NH for bug-guix@gnu.org; Thu, 07 Nov 2019 15:59:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iSoru-0000IK-M6 for bug-guix@gnu.org; Thu, 07 Nov 2019 15:59:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:35169) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iSoru-0000I6-IM for bug-guix@gnu.org; Thu, 07 Nov 2019 15:59:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iSoru-0000dF-Ex for bug-guix@gnu.org; Thu, 07 Nov 2019 15:59:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: ("=?UTF-8?Q?G=C3=A1bor?= Boskovits"'s message of "Wed, 6 Nov 2019 23:40:10 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: =?UTF-8?Q?G=C3=A1bor?= Boskovits Cc: 38088@debbugs.gnu.org Hi G=C3=A1bor, G=C3=A1bor Boskovits skribis: > Ludovic Court=C3=A8s ezt =C3=ADrta (id=C5=91pont: 2019. no= v. 6., Sze, 18:42): >> >> Hi G=C3=A1bor, >> >> G=C3=A1bor Boskovits skribis: >> >> > I did not know how to get the info better, so here is a screenshot >> > about the situation. >> > >> > 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. >> >> 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 =E2=80=9Cbroken pipe=E2= =80=9D when >> =E2=80=98guix build=E2=80=99 was talking to it, I suppose.) > > Yes, it also became corrupted. fsck on boot fixed it. > Since then it works happily again... OK. My guess is that there was maybe a transient error with your hard disk, which led the kernel to remount the root file system read-only, which in turn led to the failure of various programs, including =E2=80=98guix-daemon=E2=80=99. I=E2=80=99m closing the bug, but do reopen it if you have reasons to suspec= t a bug! Thanks, Ludo=E2=80=99.