From: Bryan Donlan <bdonlan@gmail.com>
To: Alexey Vlasov <renton@renton.name>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Counters in df, du
Date: Mon, 13 Jul 2009 15:58:36 -0400 [thread overview]
Message-ID: <3e8340490907131258g35c422ebm5a3147f9a80fd6eb@mail.gmail.com> (raw)
In-Reply-To: <20090713195558.GC5569@beaver.vrungel.ru>
2009/7/13 Alexey Vlasov <renton@renton.name>:
> On Mon, Jul 13, 2009 at 09:54:22AM -0400, Bryan Donlan 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)
>> >
>> > The most interesting is that the /tmp size constantly grows.
>>
>> lsof -n | grep deleted
>
> # lsof -n /tmp | awk '/deleted/ {if ($7 != 0) print$0}'
>
> mysqld 22905 mysql 6u REG
> 0,13 20 663938322 /tmp/ib1oZTSZ (deleted)
> mysqld 22905 mysql 8u REG
> 0,13 84773 663938424 /tmp/ibRcarbD (deleted)
>
> # df -h /tmp
> Filesystem Size Used Avail Use% Mounted on
> tmpfs 4.1G 3.4G 630M 85% /tmp
>
> It will soon be up to 100% full and I'll have to remount.
Are those the only two results? That should only be adding up to ~84kb
of space...
next prev parent reply other threads:[~2009-07-13 19:58 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
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 [this message]
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=3e8340490907131258g35c422ebm5a3147f9a80fd6eb@mail.gmail.com \
--to=bdonlan@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=renton@renton.name \
/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®