From: Andreas Dilger <adilger@shaw.ca>
To: Dan Stromberg <strombrg@dcs.nac.uci.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: huge filesystems
Date: Mon, 14 Mar 2005 11:41:37 -0500 [thread overview]
Message-ID: <20050314164137.GC1451@schnapps.adilger.int> (raw)
In-Reply-To: <pan.2005.03.09.18.53.47.428199@dcs.nac.uci.edu>
On Mar 09, 2005 10:53 -0800, Dan Stromberg wrote:
> The group I work in has been experimenting with GFS and Lustre, and I did
> some NBD/ENBD experimentation on my own, described at
> http://dcs.nac.uci.edu/~strombrg/nbd.html
>
> My question is, what is the current status of huge filesystems - IE,
> filesystems that exceed 2 terabytes, and hopefully also exceeding 16
> terabytes?
Lustre has run with filesystems up to 400TB (where it hits a Lustre limit
that should be removed shortly for a 900TB filesystem being deployed).
The caveat is that Lustre is made up of individual block devices and
filesystems of only 2TB or less in size.
> Am I correct in assuming that the usual linux buffer cache only goes to 16
> terabytes?
That is the block device limit, and also the file limit for 32-bit systems,
imposed by the size of a single VM mapping 2^32 * PAGE_SIZE.
> Does the FUSE API (or similar) happen to allow surpassing either the 2T or
> 16T limits?
Some 32-bit systems (PPC?) may allow larger PAGE_SIZE and will have a
larger limit for a single VM mapping. For 64-bit platforms there is no
2^32 limit for page->index and this also removes the 16TB limit.
> What about the "LBD" patches - what limits are involved there, and have
> they been rolled into a Linus kernel, or one or more vendor kernels?
These are part of stock 2.6 kernels. The caveat here is that there have
been some problems reported (with ext3 at least) for filesystems > 2TB
so I don't think it has really been tested very much.
Cheers, Andreas
--
Andreas Dilger
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
next prev parent reply other threads:[~2005-03-14 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 18:53 huge filesystems Dan Stromberg
2005-03-09 19:37 ` Chris Wedgwood
2005-03-09 22:01 ` Miklos Szeredi
2005-03-14 16:41 ` Andreas Dilger [this message]
2005-03-14 16:56 ` jmerkey
2005-03-15 3:21 ` Andrew Morton
2005-03-15 3:37 ` jmerkey
2005-03-15 4:02 ` Andrew Morton
2005-03-15 4:37 ` jmerkey
2005-03-15 6:04 ` Andreas Dilger
2005-03-19 11:06 ` Eric W. Biederman
2005-03-15 9:28 ` Barry K. Nathan
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=20050314164137.GC1451@schnapps.adilger.int \
--to=adilger@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=strombrg@dcs.nac.uci.edu \
/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.