linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] pvmove does not work at all with version 2.02.177(2)
Date: Mon, 11 Jun 2018 00:13:37 -0600	[thread overview]
Message-ID: <5B1E1311020000F9000223BD@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <2397dd2b-deef-2bf2-47ca-51fb6f880cf4@redhat.com>

Hi Martian,

>>> On 2018/5/30 at 18:37, in message
<2397dd2b-deef-2bf2-47ca-51fb6f880cf4@redhat.com>, Marian Csontos
<mcsontos@redhat.com> wrote:
> On 05/30/2018 11:23 AM, Gang He wrote:
>> Hello List,
>> 
>> As you know, I ever reported that lvcreate could not create a mirrored LV, 
> the root cause is a configure building item "--enable-cmirrord" was missed.
>> Now, I encounter another problem, pvmove does not work at all.
>> The detailed information/procedure is as below,
>> sle-nd1:/ # pvs
>>    PV         VG          Fmt  Attr PSize   PFree
>>    /dev/sda1  cluster-vg2 lvm2 a--  120.00g 120.00g
>>    /dev/sda2  cluster-vg2 lvm2 a--   30.00g  20.00g
>>    /dev/sdb   cluster-vg2 lvm2 a--   40.00g  30.00g
>> sle-nd1:/ # vgs
>>    VG          #PV #LV #SN Attr   VSize   VFree
>>    cluster-vg2   3   2   0 wz--nc 189.99g 169.99g
>> sle-nd1:/ # lvs
>>    LV       VG          Attr       LSize  Pool Origin Data%  Meta%  Move Log 
> Cpy%Sync Convert
>>    test-lv2 cluster-vg2 -wi-a----- 10.00g
>> sle-nd1:/ # lsblk
>> NAME                     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
>> sda                        8:0    0  160G  0 disk
>> ├─sda1                     8:1    0  120G  0 part
>> ├─sda2                     8:2    0   30G  0 part
>> └─sda3                     8:3    0   10G  0 part
>> sdb                        8:16   0   40G  0 disk
>> └─cluster--vg2-test--lv2 254:0    0   10G  0 lvm
>> vda                      253:0    0   40G  0 disk
>> ├─vda1                   253:1    0    4G  0 part [SWAP]
>> ├─vda2                   253:2    0 23.6G  0 part /
>> └─vda3                   253:3    0 12.4G  0 part /home
>> 
>> sle-nd1:/ # pvmove -i 5 -v /dev/sdb /dev/sda1
>>      Executing: /sbin/modprobe dm-mirror
>>      Executing: /sbin/modprobe dm-log-userspace
>>      Wiping internal VG cache
>>      Wiping cache of LVM-capable devices
>>      Archiving volume group "cluster-vg2" metadata (seqno 19).
>>      Creating logical volume pvmove0
>>      Moving 2560 extents of logical volume cluster-vg2/test-lv2.
>>    Increasing mirror region size from 0    to 8.00 KiB
>>    Error locking on node a431232: Device or resource busy
>>    Failed to activate cluster-vg2/test-lv2
>> 
>> sle-nd1:/ # lvm version
>>    LVM version:     2.02.177(2) (2017-12-18)
>>    Library version: 1.03.01 (2017-12-18)
>>    Driver version:  4.37.0
>>    Configuration:   ./configure --host=x86_64-suse-linux-gnu 
> --build=x86_64-suse-linux-gnu --program-prefix= --disable-dependency-tracking 
> --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin 
> --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include 
> --libdir=/usr/lib64 --libexecdir=/usr/lib --localstatedir=/var 
> --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info 
> --disable-dependency-tracking --enable-dmeventd --enable-cmdlib 
> --enable-udev_rules --enable-udev_sync --with-udev-prefix=/usr/ 
> --enable-selinux --enable-pkgconfig --with-usrlibdir=/usr/lib64 
> --with-usrsbindir=/usr/sbin --with-default-dm-run-dir=/run 
> --with-tmpfilesdir=/usr/lib/tmpfiles.d --with-thin=internal 
> --with-device-gid=6 --with-device-mode=0640 --with-device-uid=0 
> --with-dmeventd-path=/usr/sbin/dmeventd 
> --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump 
> --with-thin-repair=/usr/sbin/thin_repair --enable-applib 
> --enable-blkid_wiping
>> --enable-cmdlib --enable-lvmetad --enable-lvmpolld --enable-realtime 
> --with-default-locking-dir=/run/lock/lvm --with-default-pid-dir=/run 
> --with-default-run-dir=/run/lvm --with-clvmd=corosync --with-cluster=internal 
> --enable-cmirrord --enable-lvmlockd-dlm
>> 
>> So, I want to know if this problem is also a configuration problem when 
> building lvm2? or this problem is caused by the source code?
> 
> Hi Gang, it is an issue with the codebase, where exclusive activation 
> was required where it should not.
> 
> You will need to backport some additional patches - see CentOS SRPM. And 
> I should do the same for Fedora.
Could you help to paste the links, which are related to this back-port?

Thanks a lot.
Gang 

> 
> -- Martian
> 
>> 
>> Thanks
>> Gang
>> 
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com 
>> https://www.redhat.com/mailman/listinfo/linux-lvm 
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/ 
>> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com 
> https://www.redhat.com/mailman/listinfo/linux-lvm 
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

  reply	other threads:[~2018-06-11  6:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  9:23 [linux-lvm] pvmove does not work at all with version 2.02.177(2) Gang He
2018-05-30 10:37 ` Marian Csontos
2018-06-11  6:13   ` Gang He [this message]
2018-06-11 13:20     ` Marian Csontos
2018-06-12  2:57       ` Gang He
2018-05-30 14:12 ` Zdenek Kabelac
2018-05-31  1:53   ` Gang He

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=5B1E1311020000F9000223BD@prv1-mh.provo.novell.com \
    --to=ghe@suse.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).