From: Laurent CARON <lcaron@lncsa.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: Issue with 2.6.23 and drbd 8.0.7
Date: Tue, 18 Dec 2007 09:13:24 +0100 [thread overview]
Message-ID: <47678124.80906@lncsa.com> (raw)
In-Reply-To: <20071217233759.GB4396912@sgi.com>
David Chinner wrote:
> Hmmm - no real surprises there, but the numbers are well lower than the
> ~960MB low memory limit. I suspect that there's something at around
> 2.55am that does a filesystem traversal and that blows out the memory
> usage of these slab caches and you run out of lowmem...
Thanks David for this information,
On the previous setup (same pieces of software), we didn't had that kind
of problem.
Do you think that more memory is used while using XFS on a filesystem
traversal than with ReiserFS (the previous setup used ReiserFS)?
I'm of course not trying to blame XFS, but trying to understand what
really happens there.
Laurent
next prev parent reply other threads:[~2007-12-18 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 13:39 Issue with 2.6.23 and drbd 8.0.7 Laurent Caron
2007-12-17 22:03 ` David Chinner
2007-12-17 22:17 ` Laurent CARON
2007-12-17 23:37 ` David Chinner
2007-12-18 8:13 ` Laurent CARON [this message]
2007-12-18 12:29 ` David Chinner
2007-12-18 22:04 ` Laurent CARON
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=47678124.80906@lncsa.com \
--to=lcaron@lncsa.com \
--cc=dgc@sgi.com \
--cc=xfs@oss.sgi.com \
/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