From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#27684: Can't build disk-images or vm-images on core-updates Date: Mon, 17 Jul 2017 16:56:19 -0400 Message-ID: <20170717205619.GA2568@jasmine.lan> References: <20170713215721.GA10197@jasmine.lan> <87vamr5fh5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dXD4m-00084C-Ag for bug-guix@gnu.org; Mon, 17 Jul 2017 16:57:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dXD4h-0001cy-TP for bug-guix@gnu.org; Mon, 17 Jul 2017 16:57:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:42253) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dXD4h-0001ci-Oy for bug-guix@gnu.org; Mon, 17 Jul 2017 16:57:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dXD4g-0007Ib-Eo for bug-guix@gnu.org; Mon, 17 Jul 2017 16:57:03 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <87vamr5fh5.fsf@gnu.org> 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: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 27684@debbugs.gnu.org --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2017 at 04:02:14PM +0200, Ludovic Court=C3=A8s wrote: > The log shows that building the disk-image derivation starts with: >=20 > --8<---------------cut here---------------start------------->8--- > creating raw image of 102400.00 MiB... > Formatting '/gnu/store/yv5r65584aaml86hc0xrgyffnp70ri36-disk-image', fmt= =3Draw size=3D107374182400 > --8<---------------cut here---------------end--------------->8--- >=20 > That=E2=80=99s a lot, no? Yes, I specified it manually while debugging. > Regardless, memory consumption in the VM is not supposed to be > proportional to the size of the image being created. Indeed, the problem exists also when I don't pick a size manually. > The allocation failure happens while copying files: [...] > Does that work on previous master with Linux-libre 4.12.0 (current > master is at 4.12.2)? (This would allow us to determine if this is an > ext4 bug, who knows=E2=80=A6) Yes, I tested with a variety of kernels and on the master branch as well. > If it does, then the only other issue I can think of is if Guile itself, > while running =E2=80=98copy-recursively=E2=80=99 from (guix build utils),= eats memory > proportional to the number of files, leading to an OOM condition. > However the kernel message don=E2=80=99t report it as an OOM, AFAICS. I'm wondering if it's related to the Guile 2.0 / 2.2 mismatch in the initrd, discussed previously: https://lists.gnu.org/archive/html/guix-devel/2017-07/msg00220.html Guile 2.0 would need to rebuild all the 2.2 modules it finds. --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlltJHAACgkQJkb6MLrK fwiS9Q//ai4nn+wYS06qi+dBuMzqWd7MQM+A371JPikormprcoD1KjaTXZYR2e5z Qsue0IM/JI5J955V1wjuvxrShbf3XIEE1SfXbi/lxerWVRexv6nzqDjPTTw7nTv5 XFTFzXseQnva7/o0vehTACvsIOrQL7nC7XJV2+AxOy4Z2bFTo6Q0BabpusrCVzDq H3BSNAakxq8V682mOXE/xkfRq1WQNIXmZJpMUwljQZiWSqUTqAHlM7kNKKSy4rOW 8WbGCPwIDAsuk4PoihggetwyyzNq9bLf0fHZ2M1VrsS2xIk2oY4+ExXFpBapL6gA A2j2ZBNmiHdCVvrIPmUN3fvjBUT1RmtJMuhdM9Cwj6EdITw1A9ClE2TBjvbvKMWK ho/9IRMb6V6LB3xm8x8pgtNw+Wk33nJ62zVNUKhYh9+McJBSjIYNB3VsXE2YDXSC QicQg7cXmbDK9PA0Otq7TVq1QdRMs4Xy9sSnIJFEeXPbv3d/qZnMZRZydB8C9QVP CALokgf8sXtyx/Lt9+XP4MuzNsq8S0kzFDcFdT3UxktwqP2P6uDf2H5pT/LqhgQ2 576sehBBLON/18c/9cSnTHjJQ1nZMHrFPe46iPRu4TfaGsdyb4btXrzkwOChQRK6 S7xJzRlZZqhcEh11UQApPAy2iEzdxlXakaHieHzP2dWEw8Kwjtw= =XJ7N -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s--