All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Using pvmove with a clustered VG
Date: Fri, 13 Feb 2009 17:39:14 +0100	[thread overview]
Message-ID: <4995A232.10206@redhat.com> (raw)
In-Reply-To: <49959EEB.60900@nighthawkrad.net>


Christopher Smith wrote:
> I want to use pvmove to move some LVs in a clustered VG off some 
> specific PVs so those PVs can be removed.
> 
> The LVs are used for Xen VMs, running in a cluster of 4 Xen hosts.  The 
> PVs are LUNs on a fibre channel attached SAN.
> 
> I have constructed a test environment to try out the basic theory before 
> moving onto more specific testing on SAN-attached hosts, however, it 
> seems that LVs cannot be moved unless they are deactived:

For pvmove of active clustered volumes you need cmirror
(clustered mirror target kernel module + userspace)
(which is not available in 5.2 release, should be in 5.3)

You can use pvmove on exclusively activated volume (on one node) only.


> I also found another reply to the earlier thread, that only went to 
> linux-cluster:
> 
> http://www.mail-archive.com/linux-cluster@redhat.com/msg04365.html
> 
> pvmove  Error locking on node clustertest01.syd.nighthawkrad.net: 
> device-mapper: reload ioctl failed: Invalid argument
> pvmove  Unable to reactivate logical volume "pvmove0"
> pvmove  ABORTING: Segment progression failed.

hmmm. Can you report it to the bugzilla and attach output from lvmdump?
(to Red Hat Bugzilla, not CentOS)

Milan
--
mbroz@redhat.com

      reply	other threads:[~2009-02-13 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 16:25 [linux-lvm] Using pvmove with a clustered VG Christopher Smith
2009-02-13 16:39 ` Milan Broz [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=4995A232.10206@redhat.com \
    --to=mbroz@redhat.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.