From: Jorge Almeida <jjalmeida@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xz memory hungry?
Date: Wed, 22 Aug 2012 21:32:56 +0100 [thread overview]
Message-ID: <CAKpSnpLENT8VRJdSh7Oq0M22gsZfB13tFsm4uoeet+3z_neVAQ@mail.gmail.com> (raw)
In-Reply-To: <CA+czFiAukdRt+S5VoXbX-pep38aCZiSDNTS5XO+ZDV9YG4MzdQ@mail.gmail.com>
On Wed, Aug 22, 2012 at 8:05 PM, Michael Mol <mikemol@gmail.com> wrote:
> On Wed, Aug 22, 2012 at 2:52 PM, Jorge Almeida <jjalmeida@gmail.com> wrote:
>> # 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 distro.
>
> 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 "insane" 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 needed? I
would setup appropriate swap, if possible. The LFS site
http://www.linuxfromscratch.org/lfs/view/development/chapter03/packages.html
shows that there exists a tar.bz2 tarball. I think the ebuild should pull
that... Can't believe there are no gentooers out there with boxes with less ram.
Thanks a lot
Jorge Almeida
next prev parent reply other threads:[~2012-08-22 20:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 18:52 [gentoo-user] xz memory hungry? Jorge Almeida
2012-08-22 19:05 ` Michael Mol
2012-08-22 20:12 ` Neil Bothwick
2012-08-22 20:24 ` Michael Mol
2012-08-22 20:32 ` Jorge Almeida [this message]
2012-08-22 20:43 ` Florian Philipp
2012-08-22 21:12 ` Michael Mol
2012-08-22 21:10 ` Neil Bothwick
2012-08-22 20:39 ` Florian Philipp
2012-08-22 21:16 ` Jorge Almeida
2012-08-22 21:42 ` Michael Mol
2012-08-22 21:42 ` Michael Mol
2012-08-22 22:19 ` Jorge Almeida
2012-08-23 0:24 ` Jorge Almeida
2012-08-23 0:56 ` Michael Mol
2012-08-23 3:34 ` Paul Hartman
2012-08-23 8:37 ` Jorge Almeida
2012-08-23 9:47 ` Bill Kenworthy
2012-08-23 10:14 ` Jorge Almeida
2012-08-23 11:23 ` Blakawk
2012-08-23 11:37 ` Jorge Almeida
2012-08-23 8:22 ` Volker Armin Hemmann
2012-08-23 1:43 ` [gentoo-user] " Nikos Chantziaras
2012-08-23 8:09 ` Jorge Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKpSnpLENT8VRJdSh7Oq0M22gsZfB13tFsm4uoeet+3z_neVAQ@mail.gmail.com \
--to=jjalmeida@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox