public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Calvin Spealman <calvin@ironfroggy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Possible bug: ext3 misreporting filesystem usage
Date: Thu, 03 Jun 2004 00:49:40 +0000	[thread overview]
Message-ID: <1707149.1mCcARGuB2@ironfroggy.com> (raw)
In-Reply-To: c9l0me$cf1$1@news.cistron.nl

Miquel van Smoorenburg wrote:

> In article <1275157.LnyMtzroWT@ironfroggy.com>,
> Calvin Spealman  <calvin@ironfroggy.com> wrote:
>>I've been getting a possible bug after running my system a few weeks. The
>>ext3 partition's usage is being misreported. Right now, df -h says ive got
>>no space left, but according to du /, I'm only using 17 gigs of my 40 gig
>>drive. Restarting fixes the problem, so I'm thinking it might be some
>>mis-handled variable in memory, not something on the disc itself? And,
>>yes, I do know that du is right, not df, because I keep good track of my
>>disc usage. This is pretty serious, it killed a 40+ hour process that i'll
>>have to start over again from the beginning!
> 
> There's a process holding on to a 23 GB logfile that has been
> deleted. Try "ls -l /proc/*/fd/* 2>&1 | grep deleted" . Kill the
> process and you'll have your space back.
> 
> Mike.

All that shows is a couple things from konq's http cache, nothing adding
nearly to the 23 gigs.

If i delete some files, i have more space, but then the used space steadily
increases until i have nothing left again. i am running a 2.6.6_rc1 kernel.


  reply	other threads:[~2004-06-03  4:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02 12:31 Possible bug: ext3 misreporting filesystem usage Calvin Spealman
2004-06-02 16:53 ` Miquel van Smoorenburg
2004-06-03  0:49   ` Calvin Spealman [this message]
     [not found] <22GWW-28x-43@gated-at.bofh.it>
2004-06-07  9:19 ` Walter Hofmann

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=1707149.1mCcARGuB2@ironfroggy.com \
    --to=calvin@ironfroggy.com \
    --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