From: "Daniele P." <daniele@interline.it>
To: xfs@oss.sgi.com
Subject: Re: xfsrepair memory consumption
Date: Wed, 21 Mar 2007 09:35:07 +0100 [thread overview]
Message-ID: <200703210935.07809.daniele@interline.it> (raw)
In-Reply-To: <200703202343.KAA28746@larry.melbourne.sgi.com>
On Wednesday 21 March 2007 00:48, you wrote:
> Hi Daniele,
>
> The nlink/phase 7 patch I recently sent out does reduce this
> inode memory requirements which should address the issue you
> see.
Hi Barry,
maybe this could help. A simple ps -u during xfs_repair show
an increasing memory usage in phase 6 and 7 for 2.8.18-1.
Unfortunately with 2.6.20-1 the memory usage is exploding in
phase 2.
Regards,
Daniele P.
next prev parent reply other threads:[~2007-03-21 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 14:32 xfsrepair memory consumption Daniele P.
2007-03-20 22:13 ` David Chinner
2007-03-20 23:48 ` Barry Naujok
2007-03-21 8:35 ` Daniele P. [this message]
2007-03-21 8:34 ` Daniele P.
[not found] <200703210843.TAA08491@larry.melbourne.sgi.com>
2007-03-21 11:08 ` Daniele P.
2007-03-21 21:36 ` Chris Wedgwood
2007-03-23 8:36 ` Daniele P.
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=200703210935.07809.daniele@interline.it \
--to=daniele@interline.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.