linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Cédric Lemarchand" <cedric.lemarchand@ixcore.com>
To: Ray Morris <support@bettercgi.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Different PV on the same raid array
Date: Thu, 24 Feb 2011 14:44:55 +0100	[thread overview]
Message-ID: <4D6660D7.9000609@ixcore.com> (raw)
In-Reply-To: <20110224070435.5b057008@bettercgi.com>

Le 24/02/11 14:04, Ray Morris a écrit :
>> To bypass the DOS MBR 2TB limits, i plan to use LVM to create on the
>> > same raid array some "small" PV (< 2TB)  that will be in the same big
>> > VG (> 2TB).
>> > 
>> > First, am i planning ugly thing ? is the GPT alternative a better
>> > way ?
>    If you're not booting from the array, just make the array 
> the PV.  Once you're past the BIOS boot, there's little reason
> to have partitions at all since you're using LVM to divide the 
> storage into appropriate volumes.  If you are booting from it
> and therefore need partitions, GPT is the new standard for 
> partitions.
Ok, i am booting on but on a different partition, so i'll need to use
GPT or maybe split my array in two parts, one small for OS (using MBR)
and second for DATA (without partitions, or with GPT).
>> > i would like that LVM use 1 PV first and then
>> > the second when the first come full  (not both at the same time).
>> > Maybe LVM do that by default, or do i need some option ? (i saw
>> > "--contiguous" in the lvcreate man pages, but dont know exactly what
>> > this option does ... )
>   I think it does that by default, subject to certain other contraints
> such as not putting both halves of a mirrored LV on the same PV.

Thx for this precious informations.


Cédric

      reply	other threads:[~2011-02-24 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:51 [linux-lvm] Different PV on the same raid array Cédric Lemarchand
2011-02-24 13:04 ` Ray Morris
2011-02-24 13:44   ` Cédric Lemarchand [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=4D6660D7.9000609@ixcore.com \
    --to=cedric.lemarchand@ixcore.com \
    --cc=cedric.lemarchand@ixblue.com \
    --cc=linux-lvm@redhat.com \
    --cc=support@bettercgi.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;
as well as URLs for NNTP newsgroup(s).