From: Nathan Scott <nathans@sgi.com>
To: Aaron Peterson <aaron@alpete.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Maximum block dev size / filesystem size
Date: Mon, 11 Oct 2004 12:02:48 +1000 [thread overview]
Message-ID: <20041011120248.F4948977@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <1097244833.491.31.camel@main>; from aaron@alpete.com on Fri, Oct 08, 2004 at 10:13:53AM -0400
On Fri, Oct 08, 2004 at 10:13:53AM -0400, Aaron Peterson wrote:
> On Thu, 2004-10-07 at 15:39, Alan Cox wrote:
> > On Iau, 2004-10-07 at 21:19, Aaron Peterson wrote:
> > > 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.
> >
> > For 2.4.x 1Tb (2Tb works for some devices but its a bit variable)
> >
> > > 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.
> >
> > 2.6 fixed this problem although it appears not for some specialist
> > cases. Last time I checked LVM logical volumes over 2Tb were reported
> > problematic.
>
> I've read that the other main difficulty besides block device size
> limits is problems with the ext2 management tools themselves. So, how
> would you rate my chances of using a 2.6 kernel with XFS (and xfs
> management tools of course) with a 5 TB filesystem? Probably not a well
> tested scenerio to say the least...
Assuming the device driver(s) you pick are happy with 64 bit sector
numbers, you should expect this to work (iow, you should not have
any trouble from XFS itself). SGI ships 2.4 product with specific
supported drivers and the LBD patch (both 32 and 64 bit boxen) in
order to use large devices.
cheers.
--
Nathan
prev parent reply other threads:[~2004-10-11 2:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 20:19 Aaron Peterson
2004-10-07 19:39 ` Alan Cox
2004-10-08 14:13 ` Aaron Peterson
2004-10-11 2:02 ` Nathan Scott [this message]
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=20041011120248.F4948977@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=aaron@alpete.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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®