From: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
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 21:54:14 +0200 [thread overview]
Message-ID: <20010711215413.D20990@vestdata.no> (raw)
In-Reply-To: <3B4CA943.5EC6A127@zapmedia.com>
In-Reply-To: <3B4CA943.5EC6A127@zapmedia.com>; from Shawn Veader on Wed, Jul 11, 2001 at 03:30:11PM -0400
On Wed, Jul 11, 2001 at 03:30:11PM -0400, Shawn Veader wrote:
> 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?
No, space should be available right away, and the journal have fixed
size (32 MB pr default)
Most likely the problem is caused by a big file (or more files) beeing
deleted but some program still keeping it open. Then the space can not
be reused until that program closes the file.
You can get a list of deleted files that are still open with:
ls -l /proc/*/fd | grep deleted
--
Ragnar Kjorstad
Big Storage
next prev parent reply other threads:[~2001-07-11 19:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 19:30 disk full or not? you decide Shawn Veader
2001-07-11 19:54 ` Ragnar Kjørstad [this message]
2001-07-12 8:12 ` Hans Reiser
2001-07-11 20:16 ` Andreas Dilger
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=20010711215413.D20990@vestdata.no \
--to=kernel@ragnark.vestdata.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.