From: Maciej Zenczykowski <maze@cela.pl>
To: "Måns Rullgård" <mru@kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23 + tmpfs: where's my mem?!
Date: Thu, 11 Dec 2003 21:58:54 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0312112157540.9700-100000@gaia.cela.pl> (raw)
In-Reply-To: <yw1x3cbrh1qn.fsf@kth.se>
> FWIW, I've seen this behavior with vmware 4. The space came back when
> I closed vmware.
Vmware creates tmp files, deletes them, but keeps them open - the space is
used until all the file descriptors are closed. See if lsof doesn't show
some /tmp files which are open and large.
Cheers,
MaZe.
next prev parent reply other threads:[~2003-12-11 20:59 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 [this message]
2003-12-11 15:31 ` William Stearns
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.0312112157540.9700-100000@gaia.cela.pl \
--to=maze@cela.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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).