From: kladit@t-online.de (Klaus Dittrich)
To: linux mailing-list <linux-kernel@vger.kernel.org>
Cc: gilbertd@treblig.org, nickpiggin@yahoo.com.au, kladit@t-online.de
Subject: Re: rsync out of memory 2.6.8-rc2
Date: Mon, 19 Jul 2004 11:19:43 +0200 [thread overview]
Message-ID: <20040719091943.GA866@xeon2.local.here> (raw)
Nick your mail got lost here, sorry.
I did rsync -av xeon2:/disc1 . on the target system.
xeon2 is the system that gets out of memory.
/disc1 is 60GB and contains several thousand files.
I think this is a common backup situation.
I found out I could trigger the memory outage using du -s /disc1 too.
--
Klaus
next reply other threads:[~2004-07-19 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 9:19 Klaus Dittrich [this message]
2004-07-19 11:20 ` dentry cache leak? Re: rsync out of memory 2.6.8-rc2 bert hubert
[not found] ` <20040719113228.GA15295@outpost.ds9a.nl>
2004-07-19 12:56 ` Klaus Dittrich
2004-07-26 1:06 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-07-18 21:52 Klaus Dittrich
2004-07-19 7:48 ` Nick Piggin
2004-07-19 7:52 ` bert hubert
2004-07-19 8:47 ` 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=20040719091943.GA866@xeon2.local.here \
--to=kladit@t-online.de \
--cc=gilbertd@treblig.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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