From: bert hubert <ahu@ds9a.nl>
To: Eduard de Boer <elr.de.boer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: MD / RAID5: Memory leak?
Date: Fri, 15 Apr 2005 12:12:38 +0200 [thread overview]
Message-ID: <20050415101238.GA15358@outpost.ds9a.nl> (raw)
In-Reply-To: <30e555b5050415010015ddbcf4@mail.gmail.com>
On Fri, Apr 15, 2005 at 10:00:39AM +0200, Eduard de Boer wrote:
> I use rsync to copy a bunch of files (several GB's) to the designated
> filesystems. But after a while, all file systems get corrupted and
> 'dmesg' lists all kinds of memory corruptions in 'dm' and so on.
> Hence, the file copying stops.
That doesn't sound like a memory leak per se. Can you watch the contents of
/proc/slabinfo ? Or perhaps compare before/after a copy and check if one of
the entries has grown huge.
Also, if you are able, can you let the machine run memtest86 for a night?
Do you see activity of the OOM-killer?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
prev parent reply other threads:[~2005-04-15 10:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 8:00 Eduard de Boer
2005-04-15 10:12 ` bert hubert [this message]
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=20050415101238.GA15358@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=elr.de.boer@gmail.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
all inboxes | Powered by JetHome®