----- Original Message -----
On Thu, Sep 27, 2012 at 11:08 AM, Ayal Baron < abaron(a)redhat.com
>
wrote:
> Alan Johnson < alan(a)datdec.com > meant to write:
> So, no change.
This looks like an LVM issue. Have you tried deactivating the VG
before pvresize?
I have not, but I don't think I'll bother playing with that any more
since there is a more accepted way of growing that has no
significant down side and leaves open the potential for more
functionality. Good to know that I should not have to make the
change.
I should mention that the host is running is a minimal install of
CentOS 6.3, updated, and then tweaked by oVirt. Perhaps there is
some other package that enables this functionality?
no there isn't. LVM should work fine.
> However, as I read this email, it occurred that some other things
> might not be equal. Specifically, using multiple LUNs could provide
> a means of shrinking the storage domain in the future. LVM provides
> a simple means to remove a PV from a VG, but does the engine
> support
> this in the CLI or GUI? That is, if the a storage domain has
> multiple LUNs in it, can those be removed at a later date?
Not yet.
Does this mean it is in the works? If not, where could I put in such
feature request?
Certainly, I have no pressing need of this, but it seems like a
fairly simple thing to implement since I have done it so easily in
the past with a just a couple of commands outside of an oVirt
environment. I believe the primary purpose of the LVM functionality
was to enable removal of dying PVs before they take out an entire
VG. No reason it would not work just as well to remove a healthy PV.
It can take a long time to move all the extents off the PV
requested, but there is command to show the progress, so it would
also be easy to wrap that in to the GUI.
What's simple in a single host environment is really not that simple when it comes to
clusters.
The tricky part is the coordination between the different hosts and doing it live or with
minimal impact.