From: James Braid <jamesb@loreland.org>
To: Ralf Gross <Ralf-Lists@ralfgross.de>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: reasonable xfs fs size for 30-100 TB?
Date: Wed, 27 Jun 2007 10:57:20 +0100 [thread overview]
Message-ID: <46823480.1000305@loreland.org> (raw)
In-Reply-To: <20070626171719.GD32546@p15145560.pureserver.info>
Ralf Gross wrote:
> My main concern is the amount of RAM I need for a fsck of the xfs fs.
> Last time I search for the xfs requirements, I found the rule of
> thumb: 2 GB RAM for 1 TB of disk storage + some RAM per x inodes.
A real world example: we have a ~70TB filesystem, with ~70M inodes and
xfs_repair uses about 13-15GB of memory IIRC (haven't run a repair in a
while) using a recentish 2.8.x version.
Hope that helps.
prev parent reply other threads:[~2007-06-27 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 17:17 reasonable xfs fs size for 30-100 TB? Ralf Gross
2007-06-27 9:57 ` James Braid [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=46823480.1000305@loreland.org \
--to=jamesb@loreland.org \
--cc=Ralf-Lists@ralfgross.de \
--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.