From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id DAA92138010 for ; Wed, 22 Aug 2012 21:16:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7494021C00D; Wed, 22 Aug 2012 21:15:51 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 61C44E01BE for ; Wed, 22 Aug 2012 21:12:46 +0000 (UTC) Received: by bkwj4 with SMTP id j4so13172bkw.40 for ; Wed, 22 Aug 2012 14:12:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=2miFMOTWZpSZL/2QcxZ/haRbuzJfIUSVMOKz9auFfGM=; b=TtlKFyeTbe4UNYa4jY6SpQ5EiaBiAm+f6QMb82IDofbnmLhNxld26tk62Mawy0c9za Qm4qwRgwPYKCY3e2WRXKHX9TXYxi7WPKa71g2TPM03s4SrGtBDdsFLREC3JRFN+HIVCX eGr8Ajp2DmhxFcHCleuMDM3WisXZ4pr6PdRdu41bwXJhvkFSO3L1KNAVi/v4vVOgz1Vg R1YtXat4bm3HFfrf0bjBqnLo3fu0lJnUohp4UExaHGCYo/QxqTB+rdTFenXpwSz/fxn9 XJUQmJTGzyMDICei1ALyl3R71hEmmbWstHMrs2cF41luFBeOVbGaUITj6wTzZgvPrXxU NqNw== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.205.134.137 with SMTP id ic9mr7175314bkc.57.1345669965388; Wed, 22 Aug 2012 14:12:45 -0700 (PDT) Received: by 10.205.25.8 with HTTP; Wed, 22 Aug 2012 14:12:45 -0700 (PDT) In-Reply-To: <5035446B.8040000@binarywings.net> References: <5035446B.8040000@binarywings.net> Date: Wed, 22 Aug 2012 17:12:45 -0400 Message-ID: Subject: Re: [gentoo-user] xz memory hungry? From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 43d4d37e-a9c5-4acd-bba1-f6807a619a68 X-Archives-Hash: eaeae910997283e5054029531ca3f6c9 On Wed, Aug 22, 2012 at 4:43 PM, Florian Philipp wr= ote: > Am 22.08.2012 22:32, schrieb Jorge Almeida: >> On Wed, Aug 22, 2012 at 8:05 PM, Michael Mol wrote: >>> On Wed, Aug 22, 2012 at 2:52 PM, Jorge Almeida wr= ote: >>>> # tar -xJvf /usr/portage/distfiles/m4-1.4.16.tar.xz >>>> xz: (stdin): Cannot allocate memory >>>> >>>> The box has 2G ram + 1G swap. I'm installing Gentoo from an existing d= istro. >>> >>> How much do you have free? From xz's manpage: >> >> Almost all of it! It's a one-user workstation, which was essentialy idle= . >>> >>> >> I read the man page of xz, but it suggested nothing to me. >>> >>> Three things come to mind: >>> >>> 1) You may not have enough memory free >>> 2) There may be a bug (either compile/link-induced or code-induced) in >>> the copy of xz you're using >>> 3) Upstream used some insane settings, causing a massive increase in >>> the amount of RAM required to decompress that stream. >>> >>> >>> You could download the .tar.xz file, decompress it on a different box, >>> and then recompress it with lighter settings. >>> >>> unxz filename.tar.xz >>> xz -1 filename.tar >>> >> Done that. It extracts now, so 3) is the correct hypothesis, and "insa= ne" is >> really the appropriate word. Of course, the hash digests are now wrong, = so >> emerge still fails. Any idea how to find which amount of memory is neede= d? I >> would setup appropriate swap, if possible. [...] > > There is a table in `man xz` showing the memory requirements. Even with > the highest setting, you only need 65 MB memory for decompression (674 > MB for compression, though). Still not sure about this portion: "Still, it is possible to have .xz files= that require several giga=E2=80=90bytes of memory to decompress." But, yeah, this seems very wonky. --=20 :wq