From: Grzegorz Kulewski <kangur@polcom.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Memory and rsync problem with vanilla 2.6.7
Date: Mon, 21 Jun 2004 18:22:02 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0406211815560.16728@alpha.polcom.net> (raw)
In-Reply-To: <40D5A305.80807@yahoo.com.au>
On Mon, 21 Jun 2004, Nick Piggin wrote:
> Grzegorz Kulewski wrote:
> >>>Well it doesn't seem to have caused too much trouble as yet... But it
> >>>is the obvious candidate if your problems continue. If you are not a
> >>>bk user, the attached patch will also revert that change.
> >>
> >>Thanks, I will test it soon and I will report results. But I am not saying
> >>it is a bug - maybe it is simply change that can lead to problems with
> >>insane debug options but itself is good?
It maybe helps but very little. I can sync now one time. The second time I
always get timeouts. Without this patch I nearly never can do this one
time.
Why the kernel keeps inodes and dentries even if it completly runs out of
memory?
Thanks,
Grzegorz Kulewski
next prev parent reply other threads:[~2004-06-21 16:22 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 8:39 2.6.6-rc2-mm2 Andrew Morton
2004-04-26 16:55 ` 2.6.6-rc2-mm2 Zwane Mwaikambo
2004-04-26 17:11 ` 2.6.6-rc2-mm2 raven
2004-04-26 17:37 ` 2.6.6-rc2-bk3 (and earlier?) mount problem (?) Grzegorz Kulewski
2004-04-26 18:08 ` Linus Torvalds
2004-04-26 22:08 ` Grzegorz Kulewski
2004-04-26 22:13 ` Linus Torvalds
2004-04-26 22:38 ` Grzegorz Kulewski
2004-04-26 22:56 ` viro
2004-04-27 0:04 ` Grzegorz Kulewski
2004-04-27 0:23 ` viro
2004-04-27 0:43 ` viro
2004-04-27 1:00 ` Linus Torvalds
2004-04-27 1:07 ` 2.6.6-rc2-bk3 (and earlier?) mount problem (? viro
2004-04-27 9:12 ` Grzegorz Kulewski
2004-04-27 12:51 ` Chris Mason
2004-04-27 13:07 ` Grzegorz Kulewski
2004-04-27 14:05 ` Paul P Komkoff Jr
2004-04-27 18:34 ` viro
2004-04-27 20:04 ` Paul P Komkoff Jr
2004-04-27 20:28 ` viro
2004-04-27 20:39 ` Grzegorz Kulewski
2004-04-27 21:35 ` viro
2004-04-27 21:59 ` Grzegorz Kulewski
2004-04-28 10:19 ` Paul P Komkoff Jr
2004-06-19 16:59 ` Memory and rsync problem with vanilla 2.6.7 Grzegorz Kulewski
2004-06-19 17:50 ` Linus Torvalds
2004-06-20 3:47 ` Nick Piggin
2004-06-20 14:18 ` Grzegorz Kulewski
2004-06-20 14:41 ` Grzegorz Kulewski
2004-06-20 14:45 ` Nick Piggin
2004-06-20 20:34 ` Grzegorz Kulewski
2004-06-21 16:22 ` Grzegorz Kulewski [this message]
2004-06-20 13:24 ` Grzegorz Kulewski
2004-06-20 14:04 ` Sam Ravnborg
2004-06-21 18:36 ` network related(?) kernel panic (2.6.7-bk4) Grzegorz Kulewski
2004-04-26 18:52 ` 2.6.6-rc2-mm2 Frédéric L. W. Meunier
2004-04-26 23:06 ` 2.6.6-rc2-mm2 (compile stats) John Cherry
2004-04-28 9:37 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-29 18:41 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-29 20:45 ` 2.6.6-rc2-mm2 Andrew Morton
2004-04-29 21:18 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-30 0:24 ` 2.6.6-rc2-mm2 William Lee Irwin III
2004-04-30 2:05 ` 2.6.6-rc2-mm2 James Bottomley
2004-04-30 2:24 ` 2.6.6-rc2-mm2 William Lee Irwin III
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=Pine.LNX.4.58.0406211815560.16728@alpha.polcom.net \
--to=kangur@polcom.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=torvalds@osdl.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®