From: William Stearns <wstearns@pobox.com>
To: Willy Tarreau <willy@w.ods.org>
Cc: dual_bereta_r0x <dual_bereta_r0x@arenanetwork.com.br>,
ML-linux-kernel <linux-kernel@vger.kernel.org>,
William Stearns <wstearns@pobox.com>
Subject: Re: 2.4.23 + tmpfs: where's my mem?!
Date: Thu, 11 Dec 2003 10:31:43 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0312111027300.23867-100000@sparrow> (raw)
In-Reply-To: <20031211133124.GA18161@alpha.home.local>
Good morning, Alexandre,
On Thu, 11 Dec 2003, Willy Tarreau wrote:
> On Thu, Dec 11, 2003 at 10:54:28AM -0200, dual_bereta_r0x wrote:
> > root@hquest:/tmp# cat /etc/slackware-version
> > Slackware 9.1.0
> > root@hquest:/tmp# uname -a
> > Linux hquest 2.4.23 #6 Sat Nov 29 22:47:03 PST 2003 i686 unknown unknown
> > GNU/Linux
> > root@hquest:/tmp# df /tmp
> > Filesystem 1K-blocks Used Available Use% Mounted on
> > tmpfs 124024 112388 11636 91% /tmp
> > root@hquest:/tmp# du -s .
> > 32 .
> > root@hquest:/tmp# _
>
> maybe you have a process which creates a temporary file in /tmp, and deletes
> the entry while keeping the fd open. vmware 1.2 did that, and probably more
> recent ones still do. It's a very clever way to automatically remove temp
> files when the process terminates.
Agreed - very likely. User-Mode Linux does the same for its UML
memory images.
To see what process is doing this, try looking at:
ls -Al /proc/[0-9]*/fd/* | grep ' /tmp/'
Which will show you all open files in /tmp, deleted or not.
lr-x------ 1 wstearns wstearns 64 Dec 11 10:23 /proc/10370/fd/6 -> /tmp/sfs8eEBBc (deleted)
The pid following /proc/ (10370 in this case) is the process
holding this file open.
Cheers,
- Bill
---------------------------------------------------------------------------
"Any sufficiently advanced technology is indistinguishable from
magic."
-- Arthur C. Clark (?)
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com). Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at: http://www.stearns.org
Linux articles at: http://www.opensourcedigest.com
--------------------------------------------------------------------------
prev parent reply other threads:[~2003-12-11 15:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-11 12:54 2.4.23 + tmpfs: where's my mem?! dual_bereta_r0x
2003-12-11 13:31 ` Willy Tarreau
2003-12-11 14:11 ` Hugh Dickins
2003-12-11 14:23 ` Måns Rullgård
2003-12-11 15:01 ` Mario 'BitKoenig' Holbe
2003-12-11 15:39 ` Hugh Dickins
2003-12-11 20:58 ` Maciej Zenczykowski
2003-12-11 15:31 ` William Stearns [this message]
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=Pine.LNX.4.44.0312111027300.23867-100000@sparrow \
--to=wstearns@pobox.com \
--cc=dual_bereta_r0x@arenanetwork.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@w.ods.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;
as well as URLs for NNTP newsgroup(s).