public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: xfs@oss.sgi.com
Subject: Re: Big filesystem > (4TiB) recommendations (mkfs parameter tuning?)
Date: Sun, 21 Dec 2008 15:03:01 -0600	[thread overview]
Message-ID: <494EAF05.5020901@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.1.10.0812211551170.24116@p34.internal.lan>

Justin Piszcz wrote:
> Often, on this list, there are issues where there is not enough memory, 
> etc, to repair a large filesystem.
> 
> If one is going to create a 10-16TiB filesystem (for example), should one 
> use the mkfs.xfs defaults, or should there be special tuning for 
> filesystems of this size, so they will be less susceptible to failure for 
> one reason or another?
> 
> Justin.

Memory to repair will depend more on total inodes on the system etc, not
so much the absolute size of the filesystem.

The defaults are defaults for a reason; they are updated when warranted,
and unless you have a specific issue with them, it's best to just stick
with that.

IOW, if best practices warranted different tuning for a generic 10-16TiB
filesystem, then the defaults would need to be updated, rather than
offering hints 'n' tips on mailing lists.  :)

-Eric

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

      reply	other threads:[~2008-12-21 21:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21 20:53 Big filesystem > (4TiB) recommendations (mkfs parameter tuning?) Justin Piszcz
2008-12-21 21:03 ` Eric Sandeen [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=494EAF05.5020901@sandeen.net \
    --to=sandeen@sandeen.net \
    --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