From debbugs-submit-bounces@debbugs.gnu.org Wed Nov 06 10:52:44 2019 Received: (at 38088) by debbugs.gnu.org; 6 Nov 2019 15:52:44 +0000 Received: from localhost ([127.0.0.1]:41093 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iSNbv-0001bx-RA for submit@debbugs.gnu.org; Wed, 06 Nov 2019 10:52:44 -0500 Received: from dd26836.kasserver.com ([85.13.145.193]:34350) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iSNbt-0001bm-PT for 38088@debbugs.gnu.org; Wed, 06 Nov 2019 10:52:42 -0500 Received: from localhost (178.113.165.155.wireless.dyn.drei.com [178.113.165.155]) by dd26836.kasserver.com (Postfix) with ESMTPSA id 6A627336179E; Wed, 6 Nov 2019 16:52:39 +0100 (CET) Date: Wed, 6 Nov 2019 16:52:35 +0100 From: Danny Milosavljevic To: =?ISO-8859-1?Q?G=E1bor?= Boskovits Subject: Re: bug#38088: Guix system becomes unresponsive after backtrace Message-ID: <20191106165235.614a4d8a@scratchpost.org> In-Reply-To: References: X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-unknown-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/EBCsI1ZlWnKZGuDYM3pN7ox"; protocol="application/pgp-signature"; micalg=pgp-sha256 X-Spam-Score: -0.7 (/) X-Debbugs-Envelope-To: 38088 Cc: 38088@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.7 (-) --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--