public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Pascal <pa5ca1@gmx.de>
To: xfs@oss.sgi.com
Subject: Re: Maximum file system size of XFS?
Date: Sat, 9 Mar 2013 23:39:40 +0100	[thread overview]
Message-ID: <20130309233940.3b7c0910@thinky> (raw)
In-Reply-To: <513BB7C3.4050009@redhat.com>

Am Sat, 09 Mar 2013 17:29:23 -0500
schrieb Ric Wheeler <rwheeler@redhat.com>:

> On 03/09/2013 03:51 PM, Pascal wrote:
> > Hello,
> >
> > I am asking you because I am insecure about the correct answer and
> > different sources give me different numbers.
> >
> >
> > My question is: What is the maximum file system size of XFS?
> >
> > The official page says: 2^63 = 9 x 10^18 = 9 exabytes
> > Source: http://oss.sgi.com/projects/xfs/
> >
> > Wikipedia says 16 exabytes.
> > Source: https://en.wikipedia.org/wiki/XFS
> >
> > Another reference books says 8 exabytes (2^63).
> >
> >
> > Can anyone tell me and explain what is the maximum file system size
> > for XFS?
> >
> >
> > Thank you in advance!
> >
> > Pascal
> >
> 
> The maximum size that XFS can address (which is what most people post
> in things like wikipedia) is kind of a fantasy number.
> 
> What is a better question is what is the maximum size XFS file system
> people have in production (even better, people who have your same
> work load). Lots and lots of tiny files are more challenging than
> very large video files for example.
> 
> I think that you can easily find people with 100's of terabytes in
> production use. For Red Hat, we support production use of 100TB per
> XFS instance in RHEL6 for example since that is what we test at (and
> have been know to officially support larger instances by exception).
> 
> Some of the things to watch out for in very large file systems is how
> much DRAM you have in the server. If you ever need to xfs_repair a
> 1PB file system, you will need a very beefy box :)
> 
> Ric
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

Hello Ric,

thank you for your answer. I am aware that there is a difference
between the maximum size under practical conditions and the theoretical
maximum. But I am looking for this theoretical number to use in within
in my thesis comparing file systems.

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

  reply	other threads:[~2013-03-09 22:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 20:51 Maximum file system size of XFS? Pascal
2013-03-09 22:29 ` Ric Wheeler
2013-03-09 22:39   ` Pascal [this message]
2013-03-10  1:10     ` Eric Sandeen
2013-03-10  7:54       ` Stan Hoeppner
2013-03-11 11:02         ` Stan Hoeppner
2013-03-11 16:15           ` Hans-Peter Jansen
2013-03-11 16:22             ` Emmanuel Florac
2013-03-11  1:55     ` Dave Chinner
2013-03-11 21:45 ` Martin Steigerwald
2013-03-11 21:57   ` Martin Steigerwald
2013-03-11 22:01     ` Martin Steigerwald
2013-03-11 22:04       ` Martin Steigerwald
2013-03-20 18:26         ` Pascal
2013-03-11 22:19     ` Dave Chinner
2013-03-11 22:10   ` Martin Steigerwald

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=20130309233940.3b7c0910@thinky \
    --to=pa5ca1@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox