mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolinux.com>
To: Shawn Veader <shawn.veader@zapmedia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: disk full or not?  you decide...
Date: Wed, 11 Jul 2001 14:16:42 -0600 (MDT)	[thread overview]
Message-ID: <200107112016.f6BKGgVq009480@webber.adilger.int> (raw)
In-Reply-To: <3B4CA943.5EC6A127@zapmedia.com> "from Shawn Veader at Jul 11, 2001 03:30:11 pm"

Shawn Veader writes:
> we are using reiserfs on a system running 2.4.3  we noticed recently
> that the partition reported itself as being full. after a reboot
> the system reported having 6G freed. now again after a day of use
> the space has dissappered.
> ----
> does anyone know why this is happening? our guess is that the logs
> to reiser are getting quite large. how do we flush them and force
> a garbage collection? we save and remove several large files on this
> partition as the system is running. therefore, i figure that the
> space is kept around till the log is flushed in case it is needed for
> replaying the journal. am i totaly off?

The problem is that something is keeping these files open, and the
space cannot be freed until the process exits (or closes the files).
You can use lsof to tell you which files are open, and which process is
using them.  If it is your own code that is causing this problem, you
need to ensure that you close all of the files that you open when you
are done with them.

The reiserfs journal is a fixed size, so it cannot be that.

Note also that on reiserfs, if you have such a process which keeps
files open after they are deleted and then you have a crash, the file
is "orphaned" and the space is "lost" until you run reiserfsck again.
It may be that Chris Mason's patch for this is in the latest kernels,
but it may not be, and it might not be in the kernel you are running.

Cheers, Andreas
-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert

  parent reply	other threads:[~2001-07-11 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 19:30 Shawn Veader
2001-07-11 19:54 ` Ragnar Kjørstad
2001-07-12  8:12   ` Hans Reiser
2001-07-11 20:16 ` Andreas Dilger [this message]
2001-07-11 22:10   ` Rik van Riel
2001-07-11 22:37     ` Chris Mason
2001-07-11 20:25 ` Aaron Smith
2001-07-11 21:34   ` Josh McKinney
2001-07-13  9:52 ` disk full or not? Disk space dissapear :-( Rafael Martinez

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=200107112016.f6BKGgVq009480@webber.adilger.int \
    --to=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn.veader@zapmedia.com \
    /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®