Linux LVM users
 help / color / mirror / Atom feed
From: John Craig <johncraig01@netscape.net>
To: linux-lvm@sistina.com
Subject: [linux-lvm] LV > 2 TB ???
Date: Thu Dec 25 09:19:01 2003	[thread overview]
Message-ID: <3FEAFF9D.9020602@netscape.net> (raw)

Hi,

I asked this question on the SuSE lists, but never got a clear answer. I 
am running an AMD Opteron system, with the 64-bit 2.4.21-149-smp kernel 
and  LVM 1.0.7(mp-v6). I have a volume group of 3 RAID arrays, totalling 
2.7 TB, but I cannot create a single LV of more than 2 TB. We intend to 
grow the  storage well beyond the current size, so this is not an 
academic question.

1. I read that there is a 2 TB block device limit imposed by the kernel 
on _32-bit hardware_, but this does not have to apply to 64-bit 
hardware, if so, can I set a kernel parameter to ease that restriction?

2. Is there a setting in LVM that imposes the 2 TB limit on LVs?

3. Will these restrictions go away with the 2.6 kernel, and LVM2?

4. What advantages would I get to moving to Sistina's GFS instead of LVM 
1/2?

Thanks,

John Craig

                 reply	other threads:[~2003-12-25  9:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FEAFF9D.9020602@netscape.net \
    --to=johncraig01@netscape.net \
    --cc=linux-lvm@sistina.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