From: "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl>
To: xfs@oss.sgi.com
Subject: XFS_repair and memory consumption
Date: Thu, 26 Feb 2009 11:44:24 +0100 [thread overview]
Message-ID: <49A67288.5060301@poczta.onet.pl> (raw)
Hello
I have a few question about xfs_repair and memory consumption
I have 12 TB storage,2GB RAM and 2.6.27 32b and someday my power down.
After started system, I tried xfs_repair for this storage (because I
can`t mount this) with unsuccessful. Maybe I am in the wrong but I know
that xfs_repair need about 2GB of memory per terabyte of file system space.
Is any possible to run xfs_repair without 24GB RAM (in my case) ? Maybe
I should use big SWAP instant of so much RAM?
What is the difference running XFS_repair in 32 and 64 bit kernel?If any
difference existing, how much RAM must be in system with (for example)
64TB in single volume in order to run XFS_repair
Very thanks
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-02-26 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 10:44 aluno3 [this message]
2009-02-26 12:39 ` XFS_repair and memory consumption James Braid
2009-02-26 15:46 ` Eric Sandeen
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=49A67288.5060301@poczta.onet.pl \
--to=aluno3@poczta.onet.pl \
--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