From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Jesse Pollard <jesse@cats-chateau.net>
Cc: Tom Sightler <ttsig@tuxyturvy.com>, linux-kernel@vger.kernel.org
Subject: Re: Questions about Enterprise Storage with Linux
Date: Wed, 7 Mar 2001 22:20:25 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0103072216250.867-100000@freak.distro.conectiva> (raw)
In-Reply-To: <01030720460701.06635@tabby>
On Wed, 7 Mar 2001, Jesse Pollard wrote:
> On Wed, 07 Mar 2001, Tom Sightler wrote:
> >Hi All,
> >
> >I'm seeking information in regards to a large Linux implementation we are
> >planning. We have been evaluating many storage options and I've come up
> >with some questions that I have been unable to answer as far as Linux
> >capabilities in regards to storage.
> >
> >We are looking at storage systems that provide approximately 1TB of capacity
> >for now and can scale to 10+TB in the future. We will almost certainly use
> >a storage system that provides both fiber channel connectivity as well as
> >NFS connectivity.
> >
> >The questions that have been asked are as follows (assume 2.4.x kernels):
> >
> >1. What is the largest block device that linux currently supports? i.e.
> >Can I create a single 1TB volume on my storage device and expect linux to
> >see it and be able to format it?
>
> Checkout the GFS project for really large filesystems with a high capability
> of "fail safe" configuration.
>
> The block/file limits are more determined by the size of the hosts. Alpha/Sparc
> based systems use 64 bit operations, Intel/AMD use 32 bit. It also depends
> on usage of the sign bit in the drivers. Most 32bit systems are limited
> to 1 TB (depending on the driver of course - some allow for 2 TB).
Even on 64-bit architectures the hard upper limit is 2TB. (32-bit block
numbers)
next prev parent reply other threads:[~2001-03-08 3:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 23:13 Linux 2.4.2ac14 Alan Cox
2001-03-08 0:40 ` Greg KH
2001-03-08 0:17 ` Questions about Enterprise Storage with Linux Tom Sightler
2001-03-08 2:11 ` Jesse Pollard
2001-03-08 1:20 ` Marcelo Tosatti [this message]
2001-03-08 2:35 ` Tom Sightler
2001-03-08 6:00 ` Tim Moore
2001-03-08 5:09 ` Jauder Ho
2001-03-08 7:22 ` james rich
2001-03-09 0:29 ` Thomas Davis
2001-03-08 0:59 ` Linux 2.4.2ac14 Greg KH
2001-03-08 20:43 ` andersg
2001-03-08 0:43 ` [PATCH] " Tachino Nobuhiro
2001-03-08 1:26 ` Misspelled spinlock_prefetch for MK7 (was: Linux 2.4.2ac14) junio
2001-03-08 1:56 ` junio
2001-03-08 5:20 ` Linux 2.4.2ac14 Keitaro Yosimura
2001-03-08 12:12 ` Alan Cox
2001-03-08 7:37 ` Doug Ledford
2001-03-08 13:37 Questions about Enterprise Storage with Linux Jesse Pollard
2001-03-08 16:48 ` james rich
[not found] <Pine.LNX.4.21.0103090725030.699-100000@penguin.homenet>
2001-03-09 7:37 ` Tigran Aivazian
2001-03-09 17:30 ` Jauder Ho
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=Pine.LNX.4.21.0103072216250.867-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.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;
as well as URLs for NNTP newsgroup(s).