From: Stan Hoeppner <stan@hardwarefreak.com>
To: stan@hardwarefreak.com
Cc: Pascal <pa5ca1@gmx.de>, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: Maximum file system size of XFS?
Date: Mon, 11 Mar 2013 06:02:26 -0500 [thread overview]
Message-ID: <513DB9C2.3050408@hardwarefreak.com> (raw)
In-Reply-To: <513C3C43.7080104@hardwarefreak.com>
On 3/10/2013 1:54 AM, Stan Hoeppner wrote:
> So in summary, an Exabyte scale XFS is simply not practical today, and
> won't be for at least another couple of decades, or more, if ever. The
> same holds true for some of the other filesystems you're going to be
> writing about. Some of the cluster and/or distributed filesystems
> you're looking at could probably scale to Exabytes today. That is, if
> someone had the budget for half a million hard drives, host systems,
> switches, etc, the facilities to house it all, and the budget for power
> and cooling. That's 834 racks for drives alone, just under 1/3rd of a
> mile long if installed in a single row.
Jet lag due to time travel caused a math error above. With today's 4TB
drives it would require 2.25 million units for a raw 9EB capacity.
That's 3,750 racks of 600 drives each. These would stretch 1.42 miles,
7500 ft.
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-11 11:02 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
2013-03-10 1:10 ` Eric Sandeen
2013-03-10 7:54 ` Stan Hoeppner
2013-03-11 11:02 ` Stan Hoeppner [this message]
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=513DB9C2.3050408@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=pa5ca1@gmx.de \
--cc=sandeen@sandeen.net \
--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