From: Alexey Vlasov <renton@renton.name>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Counters in df, du
Date: Mon, 13 Jul 2009 15:32:52 +0400 [thread overview]
Message-ID: <20090713113252.GB5569@beaver.vrungel.ru> (raw)
In-Reply-To: <87fxd19cfq.fsf@basil.nowhere.org>
On Mon, Jul 13, 2009 at 11:09:29AM +0200, Andi Kleen wrote:
> Alexey Vlasov <renton@renton.name> writes:
> >
> > I know that df, du can show different values if some files were deleted,
> > but the processes which opened these files are still acting.
>
> You can check for that by doing ls -l /proc/*/fd | grep deleted
>
> It won't tell you the file size though.
There comes a big list, like this:
lowx------ 1 root root 64 Jul 13 14:58 1763 -> /tmp/ZCUDXqiMTp (deleted)
lrwx------ 1 root root 64 Jul 13 14:58 1763 -> /tmp/ZCUDXqiMTp (deleted)
lrwx------ 1 root root 64 Jul 13 14:58 1763 -> /tmp/ZCUDXqiMTp (deleted)
[cut]
lrwx------ 1 root root 64 Jul 13 15:29 317 -> /tmp/ZCUDXiOHCk (deleted)
lrwx------ 1 root root 64 Jul 13 15:29 317 -> /tmp/ZCUDXiOHCk (deleted)
lrwx------ 1 root root 64 Jul 13 15:29 317 -> /tmp/ZCUDXiOHCk (deleted)
But you can see the file date, these are new files and by next search
you won't see them any more.
The most interesting is that the /tmp size constantly grows.
--
BRGDS. Alexey Vlasov.
next prev parent reply other threads:[~2009-07-13 11:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 8:11 Alexey Vlasov
2009-07-13 9:09 ` Andi Kleen
2009-07-13 11:32 ` Alexey Vlasov [this message]
2009-07-13 11:59 ` [PATCH] Report file size for deleted files; was " Andi Kleen
2009-07-13 13:13 ` Andreas Schwab
2009-07-13 13:20 ` Andi Kleen
2009-09-03 12:32 ` Alexey Vlasov
2009-07-13 13:54 ` Bryan Donlan
2009-07-13 19:55 ` Alexey Vlasov
2009-07-13 19:58 ` Bryan Donlan
2009-07-13 20:11 ` Alexey Vlasov
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=20090713113252.GB5569@beaver.vrungel.ru \
--to=renton@renton.name \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®