From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgmerge with different physical extent sizes
Date: Fri, 24 Dec 2010 13:53:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1012241347320.23184@bmsred.bmsi.com> (raw)
In-Reply-To: <1293091697.20485.12.camel@corn.betterworld.us>
On Thu, 23 Dec 2010, Ross Boylan wrote:
> What happens if you vgmerge 2 VG's and they have different physical
> extent sizes?
The man page says it should fail. It's possible that if everything
lines up, it automatically changes the extent size of either the
source or destination VG.
It is possible to change the PE size with vgchange (some lvresizing/pvmoving
may be required and must be done manually).
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
prev parent reply other threads:[~2010-12-24 18:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 8:08 [linux-lvm] vgmerge with different physical extent sizes Ross Boylan
2010-12-24 18:53 ` Stuart D. Gathman [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=Pine.LNX.4.64.1012241347320.23184@bmsred.bmsi.com \
--to=stuart@bmsi.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).