From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Klaus Dittrich <kladit@t-online.de>
Cc: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: rsync out of memory 2.6.8-rc2
Date: Mon, 19 Jul 2004 17:48:25 +1000 [thread overview]
Message-ID: <40FB7CC9.4060302@yahoo.com.au> (raw)
In-Reply-To: <20040718215201.GA840@xeon2.local.here>
Klaus Dittrich wrote:
> rsync-2.6.2 of a large disc using 2.6.8-rc2 (I also tried 2.6.7-bk14)
> stops with "kernel: Out of Memory: Killed process xxxx" messages
> during filelist gathering.
>
> When this happens only 1.4 GB out of 2 GB RAM and no swap is used.
>
> No problems with kernel 2.6.7.
> (Peak RAM usage during filelist gathering was 1.8 GB, no swap)
>
Hi Klaus,
What arguments are you running rsync with? Also, how many files, and
how large are they?
Thanks
Nick
next prev parent reply other threads:[~2004-07-19 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 21:52 rsync out of memory 2.6.8-rc2 Klaus Dittrich
2004-07-19 7:48 ` Nick Piggin [this message]
2004-07-19 7:52 ` bert hubert
2004-07-19 8:47 ` Klaus Dittrich
-- strict thread matches above, loose matches on Subject: below --
2004-07-19 9:19 Klaus Dittrich
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=40FB7CC9.4060302@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=kladit@t-online.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