All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Pruett <joey@q7.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] changing pe size
Date: Fri, 10 Sep 2010 09:39:48 -0700	[thread overview]
Message-ID: <4C8A5F54.3060007@q7.com> (raw)

 i have looked around the net and not found much info about this...

i have a centos 5 system with a 32m pe size vg and have attached some
storage with an lvm1 4m pe size vg.  i converted the old vg to lvm2
without problem, but i would like to merge the volumes and pvmove data
onto the newer 32m pe pvs.  but you can't merge things with different pe
size, so i've been trying to get the 4m pe vg changed to 32m pe.  after
much monkeying around i was able to get all the pvs and lvs to have le
counts that were the right size to be convertible to 32m pe.  but it
looks like each segment must be sized appropriately and i can't find a
way to merge segments together so that things are sized correctly.

the most recent error is:
# vgchange -s 32m lv
  New size 209051648 for disk0 segment length not an exact number of new
extents.

would i be better off converting the 32m pe vg to 4m pe?  this is all
with lvm2 now, and what i read says that the 64k segment limit doesn't
exist anymore, so 4m pe isn't a limiting factor for lv sizing.  or is
there a way i can combine segments so they are sized appropriately? 
i've got enough space that i should be able to pvmove stuff around to
coalesce segments, but it isn't clear if there is a tool to do that.

if all else fails, i guess i'll just have to do a filesystem level copy
onto the 32m pe vg.  or is there some other magic i'm missing?

             reply	other threads:[~2010-09-10 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 16:39 Joe Pruett [this message]
2010-09-17 20:25 ` [linux-lvm] changing pe size Joe Pruett

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=4C8A5F54.3060007@q7.com \
    --to=joey@q7.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.