From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Disk usage during emerge
Date: Thu, 8 Mar 2012 22:01:57 +0200 [thread overview]
Message-ID: <20120308220157.64a7d898@khamul.example.com> (raw)
In-Reply-To: <jjakr7$fcf$1@dough.gmane.org>
On Thu, 08 Mar 2012 17:56:18 +0200
Nikos Chantziaras <realnc@arcor.de> wrote:
> On 08/03/12 16:55, Frank Steinmetzger wrote:
> > On Thu, Mar 08, 2012 at 12:50:40PM +0200, Nikos Chantziaras wrote:
> >> On 08/03/12 04:57, Frank Steinmetzger wrote:
> >>> It came to my attention that during (after) an emerge run, df
> >>> reports considerably less space available on my / than before the
> >>> emerge
> >>
> >> That's because the old files are not being deleted since they are
> >> in use. When you logout of KDE and restart the whole stack
> >> (/etc/init.d/xdm restart) then everything will be back to normal.
> >
> > By jove, that's definitely it. I knew about this fact from other
> > use cases (like deleting a video file which I'm still watching. HA,
> > do that, Windows!), but never thought of it regarding emerging. I
> > always assumed for some reason that the files were kept in RAM and
> > the physical file itself was no longer relevant. Just closing all
> > programs before logging out gave back around 350 M.
>
> I discovered this nifty little tool recently that tells you if any
> deleted files are currently being kept open by running processes:
> "app-admin/checkrestart". I usually run it after world updates so I
> can tell whether I need a restart or not.
>
>
>
Why go to the effor tof emerging another package? Use what you already
have:
lsof | egrep '(deleted)$'
--
Alan McKinnnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2012-03-08 20:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 2:57 [gentoo-user] Disk usage during emerge Frank Steinmetzger
2012-03-08 5:38 ` Paul Hartman
2012-03-08 6:08 ` Bryan Gardiner
2012-03-08 7:53 ` Julian Simioni
2012-03-08 7:54 ` Julian Simioni
2012-03-08 10:50 ` [gentoo-user] " Nikos Chantziaras
2012-03-08 14:55 ` Frank Steinmetzger
2012-03-08 15:56 ` Nikos Chantziaras
2012-03-08 20:01 ` Alan McKinnon [this message]
2012-03-08 23:42 ` walt
2012-03-09 0:05 ` Alan McKinnon
2012-03-09 0:28 ` Neil Bothwick
2012-03-09 0:29 ` Neil Bothwick
2012-03-09 6:38 ` Bryan Gardiner
2012-03-09 15:33 ` Paul Hartman
2012-03-09 16:45 ` Bryan Gardiner
2012-03-09 17:09 ` Mark Knecht
2012-03-10 2:46 ` Bryan Gardiner
2012-03-10 2:49 ` Bryan Gardiner
2012-03-10 19:27 ` Mark Knecht
2012-03-10 19:40 ` Mark Knecht
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=20120308220157.64a7d898@khamul.example.com \
--to=alan.mckinnon@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