Linux LVM users
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: linux-lvm@redhat.com
Cc: JPettey@overlandstorage.com
Subject: [linux-lvm] [JPettey@overlandstorage.com: lvm LUN size]
Date: Fri, 19 Nov 2004 12:40:23 +0100	[thread overview]
Message-ID: <20041119114022.GA21496@percy.comedia.it> (raw)

this should go to the list.
2.4 kernels have a 2TB block device limits
the lun size for lvm1 devices also depends on the number of pe per pv
that was specified at the vg creation time.

----- Forwarded message from JPettey@overlandstorage.com -----

Subject: lvm LUN size
To: bluca@comedia.it
From: JPettey@overlandstorage.com
Date: Thu, 18 Nov 2004 11:35:40 -0500
X-MIMETrack: Serialize by Router on SD-NOTES-S01/SanDiego/US 
    (Release 5.0.12  |February 13, 2003) at 11/18/2004 08:35:45 AM
X-Virus-Scanned: by amavisd-new at comedia.it
X-Spam-Status: No, hits=-0.4 tagged_above=-100.0 required=4.9 tests=BAYES_10,
 NO_REAL_NAME
X-Spam-Level: 
X-Spam-Score: -0.4

Luca -

Is the current LUN limitation for lvm 2TB? This would be in a 2.4 kernel
environment.

John Pettey
Systems Engineer
Eastern Region
301-261-4439
Overland Storage, Inc.
jpettey@overlandstorage.com
http://www.overlandstorage.com






----------------------------------------------------------------------------------------------
See our award-winning line of tape and disk-based
backup & recovery solutions at http://www.overlandstorage.com
----------------------------------------------------------------------------------------------


----- End forwarded message -----

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

                 reply	other threads:[~2004-11-19 11:40 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=20041119114022.GA21496@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=JPettey@overlandstorage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox