public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Anyone using XFS in production on > 20TiB volumes?
Date: Wed, 22 Dec 2010 09:06:20 -0800	[thread overview]
Message-ID: <20101222170620.GA29117@puku.stupidest.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1012221128440.5245@p34.internal.lan>

On Wed, Dec 22, 2010 at 11:30:05AM -0500, Justin Piszcz wrote:

> Is there anyone currently using this in production?

yes (in the past more than now)

> How much ram is needed when you fsck with a many files on such a
> volume?

didn't check specifically, but with older xfsprogs it could easily use
more than 16GB

> Is inode64 recommended on a 64-bit system?

it's for inode distribution, not 64-bit vs 32-bit system

yes, enable that ... it should be the default

> Any specific 64-bit tweaks/etc for a large 43TiB FS?

if using hw raid teach mkfs about the array geom, that coupled with
inode64 made a huge difference in performance that last time i did
this

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2010-12-22 17:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 16:30 Anyone using XFS in production on > 20TiB volumes? Justin Piszcz
2010-12-22 16:56 ` Emmanuel Florac
2010-12-22 19:03   ` Eric Sandeen
2010-12-23  0:26     ` Emmanuel Florac
2010-12-23  0:28       ` Justin Piszcz
2010-12-23  0:56         ` Dave Chinner
2010-12-23  9:43           ` Justin Piszcz
2010-12-23 12:03             ` Emmanuel Florac
2010-12-23 18:06             ` Justin Piszcz
2010-12-23 18:55               ` Emmanuel Florac
2010-12-23 19:07                 ` Justin Piszcz
2010-12-23 19:54                   ` Stan Hoeppner
2010-12-23 21:48                     ` Emmanuel Florac
2010-12-23 23:21                       ` Stan Hoeppner
2010-12-23 21:50                   ` Emmanuel Florac
2010-12-23 22:04                     ` Justin Piszcz
2010-12-23 19:29                 ` Justin Piszcz
2010-12-23 19:58                   ` Stan Hoeppner
2010-12-24  1:01                   ` Stan Hoeppner
2010-12-23 21:12               ` Eric Sandeen
2010-12-23  1:10         ` Emmanuel Florac
2010-12-22 17:06 ` Chris Wedgwood [this message]
2010-12-22 17:10   ` Justin Piszcz
2010-12-22 17:32     ` Chris Wedgwood
2010-12-22 17:35       ` Justin Piszcz
2010-12-22 18:50         ` Chris Wedgwood
2010-12-22 19:24           ` Justin Piszcz

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=20101222170620.GA29117@puku.stupidest.org \
    --to=cw@f00f.org \
    --cc=jpiszcz@lucidpixels.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