Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] questions
Date: Thu, 8 Feb 2001 21:35:53 +0000	[thread overview]
Message-ID: <20010208213553.A19468@srv.sistina.com> (raw)
In-Reply-To: <20010208205551.C21949@vestdata.no>; from lvm@ragnark.vestdata.no on Thu, Feb 08, 2001 at 08:55:51PM +0100

On Thu, Feb 08, 2001 at 08:55:51PM +0100, Ragnar Kj�rstad wrote:
> Hi
> 
> Is there a limit for the maximum size of a LVM diskgroup?
> (internally in LVM-code, or because of other limits in the kernel)
> The 2TB (1 TB) maximum devicesize in the linux-kernel doesn't apply, does
> it?

256 (which is limited to 128 SCSI disks and 20? IDE discs) * maximum PV size
which is limited to 2 TB --> 296 TB in case you'll find 2 TB IDE disks ;-)

> 
> How does LVM handle that one of it's devices changes size? E.g. if one
> of the physical disks is a RAIDset, and more disks are added to it?
> Is there any way to tell LVM to use more or less of the disk?

LVM can't handle size changes directly today.
You need to go with

   a. additional partitions on the size increased device
   b. additional LUNs exposing the added capacity (typical with some
      HW RAID device models)

and create additional PVs on them.

Basically we could implement an enhancement to pvchange(8) in order
to support growing of PVs.

> 
> 
> Thanks.
> 
> 
> -- 
> Ragnar Kj�rstad
> BigStorage
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-02-08 21:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-08 19:55 [linux-lvm] questions Ragnar Kjørstad
2001-02-08 21:35 ` Heinz J. Mauelshagen [this message]
2001-02-08 22:44 ` Andreas Dilger
2001-02-08 23:30   ` Ragnar Kjørstad
2001-02-09  0:05     ` Andreas Dilger
2001-02-09  8:34       ` Christoph Hellwig
2001-02-09 11:21         ` Heinz J. Mauelshagen
  -- strict thread matches above, loose matches on Subject: below --
2001-11-05 17:08 Magosanyi Arpad
2001-11-07 19:26 ` Wolfgang Weisselberg
2001-11-08  2:23   ` Heinz J . Mauelshagen
2001-11-11 14:28     ` Wolfgang Weisselberg
2007-03-04  1:59 [linux-lvm] Questions Stuart D. Gathman
2007-03-05 11:53 ` Heinz Mauelshagen
2007-03-05 17:31   ` Stuart D. Gathman
2007-03-05 17:41   ` Stuart D. Gathman

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=20010208213553.A19468@srv.sistina.com \
    --to=mauelshagen@sistina.com \
    --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