mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Dan Stromberg <strombrg@dcs.nac.uci.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: huge filesystems
Date: Wed, 9 Mar 2005 11:37:28 -0800	[thread overview]
Message-ID: <20050309193728.GA7070@taniwha.stupidest.org> (raw)
In-Reply-To: <pan.2005.03.09.18.53.47.428199@dcs.nac.uci.edu>

On Wed, Mar 09, 2005 at 10:53:48AM -0800, Dan Stromberg wrote:

> My question is, what is the current status of huge filesystems - IE,
> filesystems that exceed 2 terabytes, and hopefully also exceeding 16
> terabytes?

people can and do have >2T filesystems now.  some people on x86 have
hit the 16TB limit and others are large still with 64-bit CPUs

> Am I correct in assuming that the usual linux buffer cache only goes
> to 16 terabytes?

for 32-bit CPUs

> 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?

LBD is in 2.6.x and is required for >2TB but sometimes that means >1TB
or even smaller depending on the drivers

many drivers simply won't go above 2T even with CONFIG_LBD so you need
to poke about and see what works for you (or use md/raid to glue
together multiple 2TB volumes)

  reply	other threads:[~2005-03-10  6:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 18:53 Dan Stromberg
2005-03-09 19:37 ` Chris Wedgwood [this message]
2005-03-09 22:01 ` Miklos Szeredi
2005-03-14 16:41 ` Andreas Dilger
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=20050309193728.GA7070@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®