From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S5b44-0005Bu-4M for garchives@archives.gentoo.org; Thu, 08 Mar 2012 10:59:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D5EA1E0757; Thu, 8 Mar 2012 07:54:09 +0000 (UTC) Received: from mail-vw0-f53.google.com (mail-vw0-f53.google.com [209.85.212.53]) by pigeon.gentoo.org (Postfix) with ESMTP id BCF82E0662 for ; Thu, 8 Mar 2012 07:53:05 +0000 (UTC) Received: by vbbfc26 with SMTP id fc26so194266vbb.40 for ; Wed, 07 Mar 2012 23:53:05 -0800 (PST) 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=0alsqohib9rwaURB8iAY+TxBTaZRftcYATf21DcPDlw=; b=VIQBktNZk6tlff3zlFCzg7EbLRUtb+o/ydcU+6r1HqUlLMMr7g16KRbu7n21/5vzuF d/urTIr7/gN6LqJtQbFbv3ht5I6IuCnJlZJ7K/dW9y3nUXKMg5gGhH5Zy2Bjl55jmcee FHWJuVRddt4K5BA57lwwCfSWDwUjKsP8jVj1ELsnya2p6reb2b8ryTnzND8YL/3h5eEA 8KyrvWMg9iUOYzMfI7zxVP/qrMMH8qk13bg75DhpJsXbEn6xwrnLTG6EcV2WobPfSJI3 jOXePOoCxp4JjmYoVxiiKrkUteVSuD7dQVNATNJuI8kZIVfVhAoyAyID34oxc6TrbdqG QeOw== 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.52.27.70 with SMTP id r6mr8293743vdg.41.1331193185319; Wed, 07 Mar 2012 23:53:05 -0800 (PST) Received: by 10.52.28.19 with HTTP; Wed, 7 Mar 2012 23:53:05 -0800 (PST) In-Reply-To: <20120308025700.GA11477@eisen.lan> References: <20120308025700.GA11477@eisen.lan> Date: Wed, 7 Mar 2012 23:53:05 -0800 Message-ID: Subject: Re: [gentoo-user] Disk usage during emerge From: Julian Simioni To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: bbac51cb-1ec4-4208-a522-191592191edf X-Archives-Hash: d6bf22f83208cf380e52d1793d606469 On Wed, Mar 7, 2012 at 6:57 PM, Frank Steinmetzger wrote: > > Hello list > > It came to my attention that during (after) an emerge run, df reports > considerably less space available on my / than before the emerge (everyth= ing > except /home sits on the root partition). I was wondering how this comes = to > be, since I have /var/tmp/portage on tmpfs. > > I am in the middle of a KDE upgrade (4.8.0=E2=86=924.8.1) right now and b= efore I > started, I downloaded all distfiles and then looked at df /, it showed 10= 22 > blocks, hence about 1 GB of free disk space. I am at package 115 out of 1= 74 > right now, and df shows a mere 389k blocks remaining. > > Also before I began the emerge run, I started 'ncdu -x /' which scans all= dirs > on the / partition and then I can browse through my FS hieararchy, showin= g the > disk usage of every directory. Now I ran the same ncdu command again in > another screen, so I can compare it with the first one. > > The folders themselves have 0.1 to 0.2 GB difference between their old an= d new > state, and ncdu's bottom bar even shows the same values for both apparent= and > real total disk usage (rounded to 0.1 GB). So what am I missing here? I > searched df's man page for something about apparent sizes/sparse files, b= ut > then again, why would portage create such files in the first place? > > Do you have any thoughts that might help me understand what I'm seeing? > -- > Gru=C3=9F | Greetings | Qapla' > I forbid any use of my email addresses with Facebook services. > > You will find everything in an online database. > Just not what you are looking for. Unless you have it mounted on tmpfs for increased compilation speed as many others do, /var/tmp/portage can easily grow to several hundred megabytes as packages are compiled. Once the compilation finishes successfully, it will be cleaned up, so the contents are constantly changing during an emerge, and it may not be easy to track down after the fact.