All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Smyth <scotts@cuttedge.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Doubts about LVM2 real limits
Date: Wed, 07 Feb 2007 07:53:32 -0800	[thread overview]
Message-ID: <45C9F5FC.8060200@cuttedge.com> (raw)
In-Reply-To: <200702071509.l17F9TiU012582@mx2.redhat.com>

We have done >100 TB without a problem in a VG and in
a single LV.  The problem is with file system selection if you
are using this large a LV as a file system.  You are limited to
XFS or JFS w/o venturing into ext4 and reiserfs4 which
some people view as experimental still.

We can only speak for XFS on a 100 TB file system.  We have
yet to try ext4 or reiserfs4 as a commercial file system.

3 Xyratex FC RAID controllers w/ expansion chassis attached.
4 Gb/s QLogic controllers.

linux-2.6.17.14
device-mapper-1.02.13
LVM2-2.02.16

Sincerely,
Scott

Cesar O. Pablo wrote:
> Hi,
>
>
>  We have plans to build a 30TB aprox. data storage using a set of SAN boxes configured as 
> RAID 5, our understanding is that using LVM2 with Red Hat 4 and our 64 bit AMD opteron 
> processors shall allow us to do that. Our concern is to know in advance if our approach is 
> wrong or even better if somebody else has been successfully taking the same road before.
>
>  Documentation tells us that the limit is in the order of the 8 Exabytes (8TB for IA-32) 
> but this is not enough as this is a go / no go decision.
>
>   Thanks for any help or pointer to a similar rig.
>
>  Cesar O. Pablo
>  
>
>
>
>
> Cesar
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>   

      reply	other threads:[~2007-02-07 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 15:09 [linux-lvm] Doubts about LVM2 real limits Cesar O. Pablo
2007-02-07 15:53 ` Scott Smyth [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=45C9F5FC.8060200@cuttedge.com \
    --to=scotts@cuttedge.com \
    --cc=linux-lvm@redhat.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 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.