From: Alex Elder <aelder@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] repair: warn if running in low memory mode
Date: Wed, 05 Jan 2011 16:25:07 -0600 [thread overview]
Message-ID: <1294266307.2312.87.camel@doink> (raw)
In-Reply-To: <1294121563-17150-1-git-send-email-david@fromorbit.com>
On Tue, 2011-01-04 at 17:12 +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> When checking large filesystems, xfs_repair makes an estimate of how
> much RAM it will need to execute effectively. If the amount of RAM
> is less than this, it reduces the bhash size and turns of
> prefetching, which will substantially slow down the repair process.
> Add a warning that indicates this is happening, along with a
> recommendation of how much RAM repair calculates it needs to run
> with prefetching enabled.
This looks good.
If someone specifies a maximum memory amount using -m,
but that amount exceeds the memory available and/or the
process' address space rlimit, it is silently reduced
to the maximum possible. That may then be followed by
the "...please increase it..." message, which might be
confusing and possibly annoying. Maybe a single message
that was a bit more informative would suffice, whether
or not max_mem was specified.
Just a thought. Your change looks fine.
Reviewed-by: Alex Elder <aelder@sgi.com>
> Signed-off-by: Dave Chinner <dchinner@redhat.com>
> ---
> repair/xfs_repair.c | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/repair/xfs_repair.c b/repair/xfs_repair.c
> index e36eeae..eea1b34 100644
> --- a/repair/xfs_repair.c
> +++ b/repair/xfs_repair.c
> @@ -650,12 +650,20 @@ main(int argc, char **argv)
> * Turn off prefetch and minimise libxfs cache if
> * physical memory is deemed insufficient
> */
> - if (max_mem_specified)
> + if (max_mem_specified) {
> do_abort(_("Required memory for repair is "
> "greater that the maximum specified "
> "with the -m option. Please increase "
> "it to at least %lu.\n"),
> mem_used / 1024);
> + } else {
> + do_warn(_("Not enough RAM available for repair "
> + "to enable prefetching. This will be "
> + "_slow_.\n"
> + "You need at least %luMB RAM to run "
> + "with prefetching enabled."),
> + mem_used * 1280 / (1024 * 1024));
> + }
> do_prefetch = 0;
> libxfs_bhash_size = 64;
> } else {
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-01-05 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 6:12 [PATCH] repair: warn if running in low memory mode Dave Chinner
2011-01-04 9:52 ` Christoph Hellwig
2011-01-05 22:25 ` Alex Elder [this message]
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=1294266307.2312.87.camel@doink \
--to=aelder@sgi.com \
--cc=david@fromorbit.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