linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Cédric Lemarchand" <cedric.lemarchand@ixcore.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Different PV on the same raid array
Date: Thu, 24 Feb 2011 11:51:26 +0100	[thread overview]
Message-ID: <4D66382E.4090906@ixcore.com> (raw)

Hello,

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 ?

Secondly, I dont know how LVM use PVs within a VG, but for performances
issues, 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 ... )


Thx

Cédric

             reply	other threads:[~2011-02-24 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 10:51 Cédric Lemarchand [this message]
2011-02-24 13:04 ` [linux-lvm] Different PV on the same raid array Ray Morris
2011-02-24 13:44   ` Cédric Lemarchand

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=4D66382E.4090906@ixcore.com \
    --to=cedric.lemarchand@ixcore.com \
    --cc=cedric.lemarchand@ixblue.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;
as well as URLs for NNTP newsgroup(s).