From: Andreas Dilger <adilger@clusterfs.com>
To: Roman Dementiev <dementiev@mpi-sb.mpg.de>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: buffer leakage in kernel?
Date: Fri, 24 Jan 2003 11:07:27 -0700 [thread overview]
Message-ID: <20030124110727.N12662@schatzie.adilger.int> (raw)
In-Reply-To: <3E31364E.F3AFDCF0@mpi-sb.mpg.de>; from dementiev@mpi-sb.mpg.de on Fri, Jan 24, 2003 at 01:49:18PM +0100
On Jan 24, 2003 13:49 +0100, Roman Dementiev wrote:
> I've met with following problem (kernel 2.4.20-pre4 ):
> I write and read sequentially from/to 8 files each of 64 Gbytes (not a
> mistake, 64 Gbyte),
> each on different disk. The files are opened with flag O_DIRECT. I have
> 1 Gbyte RAM, no swap.
> While this scanning is running, number of "buffers" reported by ''free"
> and in /proc/meminfo
> is continuously increasing up to ~ 500 MB !! When the program exits
> normally or I break it, number
> of "buffers" does not decrease and even increases if I do operations on
> other files.
>
> This is not nice at all when I have another applications running
> with memory consumption > 500 MB: when my "scanner" approaches 50G
> border on each disk, I've got numerous "Out of memory" murders :(.
> Even 'ssh' to this machine is killed :(
There was a bug in vanilla 2.4.18 related to O_DIRECT that is fixed in the
RH kernel, but I don't know when/if it was merged into the main kernel.
As always, testing with the most recent kernel (2.4.21-pre3 currently)
will tell you whether that bug has been fixed already or not.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2003-01-24 17:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 12:49 Roman Dementiev
2003-01-24 18:07 ` Andreas Dilger [this message]
2003-01-24 21:02 ` Andrew Morton
2003-01-27 16:57 ` Roman Dementiev
2003-01-27 20:51 ` Andrew Morton
2003-02-04 12:58 ` Roman Dementiev
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=20030124110727.N12662@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=dementiev@mpi-sb.mpg.de \
--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
all inboxes | Powered by JetHome®