From: Jag <agrajag@linuxpower.org>
To: Giuliano Pochini <pochini@denise.shiny.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Temporary disk space leak
Date: Sun, 1 Apr 2001 12:49:58 -0700 [thread overview]
Message-ID: <20010401124958.A13901@kotako.analogself.com> (raw)
In-Reply-To: <3AC5A16A.9F0147E4@denise.shiny.it>
In-Reply-To: <3AC5A16A.9F0147E4@denise.shiny.it>; from pochini@denise.shiny.it on Sat, Mar 31, 2001 at 11:20:42AM +0200
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
On Sat, 31 Mar 2001, Giuliano Pochini wrote:
>
> [root@Jay Giu]# du -c /home
> [...]
> 320120 /home
> 320120 total
> [root@Jay Giu]# df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/sda8 253823 65909 174807 27% /
> /dev/sda7 2158320 750672 1296240 37% /usr
> /dev/sda5 2193082 1898198 183474 91% /home
> /dev/sda9 1013887 899924 61586 94% /opt
>
>
> It happened after I wrote and deleted very large files (~750MB) a
> few times in my home dir.
> Then I logged out and I relogged in as root to check what happened
> and "df" shown everything was right again:
>
> /dev/sda5 2193082 320122 1761550 15% /home
>
>
> ...strange...
Was the 750M file opened by a program when it was deleted? When a file
is deleted, if it is opened, it will still be there and taking up file
space (as shown in df) until it is completely closed. However, even if
the file is opened by a process and not really deleted, the file's space
will no longer show up in du because the file can no longer be accessed
through the filesystem.
It sounds like this is what happened, and whatever program had the file
open was closed when you logged out.
Jag
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-04-01 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-31 9:20 Giuliano Pochini
2001-04-01 19:49 ` Jag [this message]
2001-04-02 7:14 ` Giuliano Pochini
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=20010401124958.A13901@kotako.analogself.com \
--to=agrajag@linuxpower.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pochini@denise.shiny.it \
/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®