All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Peterson <aaron@alpete.com>
To: linux-kernel@vger.kernel.org
Subject: Maximum block dev size / filesystem size
Date: Thu, 07 Oct 2004 16:19:21 -0400	[thread overview]
Message-ID: <1097180361.491.25.camel@main> (raw)

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

I work for a company with a 15 TB SAN.  All opinions about the
disadvantages of creating really large filesystems aside, I'm trying to
find out what is the maximum filesystem size we can allocate on our SAN
that a linux box (x86) can really use.

I seem to be finding (from various posts on newsgroups and the kernel
source itself) that block devices with 2.4 kernels cannot exceed 2 TB,
so no matter what the filesystem can theoretically handle, 2 TB is the
practical limit.

I've read that XFS filesystems can theoretically be created up to 18
million TB in size.

What I can't seem to find anywhere is whether the 2 TB block device
limit has improved/grown with 2.6 kernels (on x86 hardware).  Perhaps
I've looked in the wrong places, but I haven't found anything.

If you have any helpful information, or can point me towards a better
place to look I would be very appreciative.

I am not joined to this list, so if you can CC: me in the reply I would
also be grateful.

Aaron

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

             reply	other threads:[~2004-10-07 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 20:19 Aaron Peterson [this message]
2004-10-07 19:39 ` Maximum block dev size / filesystem size Alan Cox
2004-10-08 14:13   ` Aaron Peterson
2004-10-11  2:02     ` Nathan Scott

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=1097180361.491.25.camel@main \
    --to=aaron@alpete.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.