From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: bug#38088: Guix system becomes unresponsive after backtrace Date: Wed, 6 Nov 2019 16:52:35 +0100 Message-ID: <20191106165235.614a4d8a@scratchpost.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/EBCsI1ZlWnKZGuDYM3pN7ox"; protocol="application/pgp-signature"; micalg=pgp-sha256 Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:50794) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSNcH-0005mA-CR for bug-guix@gnu.org; Wed, 06 Nov 2019 10:53:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iSNcG-0006xK-AR for bug-guix@gnu.org; Wed, 06 Nov 2019 10:53:05 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:60505) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iSNcE-0006vb-Ej for bug-guix@gnu.org; Wed, 06 Nov 2019 10:53:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iSNcE-0001ce-Av for bug-guix@gnu.org; Wed, 06 Nov 2019 10:53:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: 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 --Sig_/EBCsI1ZlWnKZGuDYM3pN7ox Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi G=C3=A1bor, On Wed, 6 Nov 2019 15:15:41 +0100 G=C3=A1bor Boskovits 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? --Sig_/EBCsI1ZlWnKZGuDYM3pN7ox Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl3C7EMACgkQ5xo1VCww uqXHfwf/VmXKpfn4vPU6+d/KftehDAfZrjLCp9h2zo8hZYe67D/UAYM71jhKRI0t SliQLYR5kIF93DnNjVrRcVDG8FTMVQ9QZIjwxhiUKxqBlK7bKFo2eV7pqG76lRQl ZWP+VdD2gYAxSB0uT4DyiwV+G3w8Hfv8SnEd+LQNj4HLyrMCVb1mkzPt9DfcmbtH iU6esIX32vWGfyDYmAZdHKKZ2Lr1T4eXU24Ty3RA/TR5QCdRmykQEHizFuq/eITp l4VJxcb4CUs0ijtsWacY6IrfWz2WUeoGrriMin3HEMRgDzddH56Vd1+cY3rwlKCe ZoUzh5t5lgr/wvv16pRQJM40csm+qA== =yAZl -----END PGP SIGNATURE----- --Sig_/EBCsI1ZlWnKZGuDYM3pN7ox--