🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: fa.netbsd.tech.kern
Article #71

Re: pbulk using tmpfs

#71
From: Jan Danielsson
Date: Sat, 20 Apr 2013 23:08
22 lines
3627 bytes
On 04/21/13 00:51, iMil wrote:
> Nevertheless, I really wonder what will happen in case of WRKOBJDIR
> being "full", will I just see a "no space left on device"? Will the
> system be able to even run a cleanup? Won't it be then in a state of
> thrashing?

   If you limit the space of the tmpfs, and run into the limitation,
you'll get "no space left on device". A cleanup shouldn't be a problem,
and should recover the memory.

   If you don't limit the space and you run out of memory, the build
will typically fail due to a tool running out of memory. (On my 2GB
machine it used to happen when linking parts of qemu, but that doesn't
happen with recent versions). Back when it used to happen, I could
recover the space using "make clean". (It used vast amounts of memory
while trying to link, and that (freed) memory was more than enough fit
the "make clean" sub-processes).


-- 
Kind regards,
Jan Danielsson
Technical Details
Message-ID: <fa.5NAkJjoZEGeHlhK4JwZe/C3PIWY@ifi.uio.no>
Path: arc1-ca.pugleaf.net!oi7ni177pbb.0!nntp.google.com!news.glorb.com!uio.no!nntp.uio.no!.POSTED!not-for-mail
References: <fa.qbJt8BWJHb0rQuduJvUuC025qgM@ifi.uio.no> <fa.bS2cJNCT2gg8lK4dH+G1/WvpDy4@ifi.uio.no>

Show Full Headers
Complete Article Headers
X-Google-Thread: 10c6f4,786e9905c90c1180
X-Google-NewGroupId: yes
X-Google-Attributes: gidb7e13b6095,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.66.225.230 with SMTP id rn6mr1555519pac.26.1366499325332;
        Sat, 20 Apr 2013 16:08:45 -0700 (PDT)
Path: arc1-ca.pugleaf.net!oi7ni177pbb.0!nntp.google.com!news.glorb.com!uio.no!nntp.uio.no!.POSTED!not-for-mail
From: Jan Danielsson <jan.m.danielsson@gmail.com>
Newsgroups: fa.netbsd.tech.kern
Subject: Re: pbulk using tmpfs
Date: Sat, 20 Apr 2013 23:08:44 UTC
Organization: La Cosa Nostra
Lines: 23
Sender: tech-kern-owner@NetBSD.org
Message-ID: <fa.5NAkJjoZEGeHlhK4JwZe/C3PIWY@ifi.uio.no>
References: <fa.qbJt8BWJHb0rQuduJvUuC025qgM@ifi.uio.no> <fa.bS2cJNCT2gg8lK4dH+G1/WvpDy4@ifi.uio.no>
NNTP-Posting-Host: mail-jess.uio.no
Mime-Version: 1.0
X-Trace: readme.uio.no 1366499324 19868 129.240.7.9 (20 Apr 2013 23:08:44 GMT)
X-Complaints-To: abuse@uio.no
NNTP-Posting-Date: Sat, 20 Apr 2013 23:08:44 +0000 (UTC)
User-Agent: Mozilla/5.0 (X11; NetBSD amd64; rv:17.0) Gecko/20130413 Thunderbird/17.0.5
Cc: tech-kern@NetBSD.org, tech-pkg@NetBSD.org
To: iMil <imil@home.imil.net>
Delivered-To: tech-kern@netbsd.org
X-Virus-Scanned: amavisd-new at NetBSD.org
Authentication-Results: mail.NetBSD.org (amavisd-new);
 dkim=pass (2048-bit key) header.d=gmail.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=x-received:message-id:date:from:organization:user-agent
         :mime-version:to:cc:subject:references:in-reply-to
         :x-enigmail-version:openpgp:content-type:content-transfer-encoding;
        bh=ElpMMKOTWdY+tUbqCXP3/gQUZ2fCFGRuDIqP5LP2G94=;
        b=Nl9J8SJFQ4E7TnjIQOwjXcYUgcq7wHMfmpryj2IeyLSLD3Qux0L5HU9lCInQE2o3UY
         fyO2RsjwPT1svmVmVPXvn0D6QtmAk8yUyxQydhQ3HYmFoiemDXnLm1u0h3Uom0Rj3BdS
         pVeEaaFXoXjGlk8LFsVYfAIPqkCEAnDZZ81Bkr3Zxrnfi2/vXa5nVrL7i/tEdMVwGChS
         kky+agcLwHGcL7jwEvvUeCYZ/X9QsrOov6dDXWdE45BRuU2HfcIZKBkkJMbwLUTXqtqq
         ABu14hFu2eDI76K7Ux2rzc2rVBpR1eyKApoGBZz49iib6Ma4NbqY+gp9NgZVyJVRxDlx
         qecw==
X-Received: by 10.112.150.34 with SMTP id uf2mr10587170lbb.1.1366498813812;
        Sat, 20 Apr 2013 16:00:13 -0700 (PDT)
In-Reply-To: <alpine.NEB.2.00.1304210044190.19430@korriban.imil.net>
X-Enigmail-Version: 1.5a1pre
OpenPGP: id=13D7A8ED
List-Id: tech-kern.NetBSD.org
Original-Date: Sun, 21 Apr 2013 01:00:10 +0200
Original-Message-Id: <51731DFA.8030205@gmail.com>
Original-References: <20130420221716.93FF8604E9@jupiter.mumble.net> <alpine.NEB.2.00.1304210044190.19430@korriban.imil.net>
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit