Re: [linux-lvm] compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure failed. For help, thanks

2018-04-04 Thread Guozhonghua 

Hi, All

I add one file as below, so compiled it successfully. 

root@u610:/usr/lib/x86_64-linux-gnu/pkgconfig# cat libsanlock_client.pc 
prefix=/usr
exec_prefix=/usr
libdir=${prefix}/lib/x86_64-linux-gnu
includedir=${prefix}/include

Name: libsanlock_client
Version: 3.3.0-2.1
Description: libsanlock_client
Requires: corosync
Cflags: -I${includedir}

While compile the code, I found one bug in the file, so there is one patch 
about. 

+   int lv_info_with_seg_status(struct cmd_context *cmd,
+const struct lv_segment *lv_seg,
+struct lv_with_info_and_seg_status *status,
+int with_open_count, int with_read_ahead)
-   int lv_info_with_seg_status(struct cmd_context *cmd, const struct 
logical_volume *lv,
-   const struct lv_segment *lv_seg, int 
use_layer,
-   struct lv_with_info_and_seg_status *status,
-   int with_open_count, int with_read_ahead)
{
return 0;
}


Thanks. 
Guozhonghua.  



> -邮件原件-
> 发件人: guozhonghua (Cloud)
> 发送时间: 2018年3月30日 16:34
> 收件人: 'linux-lvm@redhat.com'
> 主题: compile lvm2 with --enable-lvmlockd-sanlock on Ubuntu 1710, configure
> failed. For help, thanks
> 
> 
> Hi,
> 
> I want to have a test of lvmlockd, while try to compile the lvm2, which 
> version is
> LVM2.2.02.177, or 2.2.02.168.
> 
> With the configure:
> ./configure --enable-cmirrord --enable-debug --disable-devmapper
> --enable-lvmetad --enable-lvmpolld --enable-lvmlockd-sanlock --enable-dmeventd
> --enable-udev_sync --enable-cmdlib
> 
> But failed as below with configure error check:
> 
> checking for LOCKD_SANLOCK... no
> configure: error: bailing out
> 
> The environment is Ubuntu 1710.
> 
> And I had install the sanlock as below:
> root@u610:~/LVM2.2.02.177# dpkg -l |grep sanlock
> ii  libsanlock-client1 3.3.0-2.1
> amd64Shared storage lock manager (client library)
> ii  libsanlock-dev 3.3.0-2.1
> amd64Shared storage lock manager (development files)
> ii  libsanlock13.3.0-2.1
> amd64Shared storage lock manager (shared library)
> ii  libvirt-sanlock3.6.0-1ubuntu5
> amd64Sanlock plugin for virtlockd
> ii  python-sanlock 3.3.0-2.1
> amd64Python bindings to shared storage lock manager
> ii  sanlock3.3.0-2.1
> amd64Shared storage lock manager
> 
> Is there something wrong with it?
> 
> Thanks

___
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/

Re: [linux-lvm] PVmove can not work on lvm2-2.02.177

2018-04-04 Thread Gang He 
Hi Zdenek,

>>> Zdenek Kabelac  04/03/18 4:11 PM >>>
Dne 3.4.2018 v 04:28 Gang He napsal(a):
> Hello list,
> 
> As you know, pvmove can run on old version (e.g. lvm2-2.02.120 on SLE12SP2),
> But with new version lvm2-2.02.177, I can not run pvmove successfully in the 
> cluster.
> Here, I paste some information from my test,
> if you can know the cause, please help to figure out.
> 
> tb0307-nd1:/ # cat /etc/issue
> Welcome to openSUSE Tumbleweed 20180307 - Kernel \r (\l).
> tb0307-nd1:/ # uname -r
> 4.15.7-1-default
> tb0307-nd1:/ # rpm -qa | grep lvm
> lvm2-cmirrord-2.02.177-4.1.x86_64
> liblvm2app2_2-2.02.177-4.1.x86_64
> liblvm2cmd2_02-2.02.177-4.1.x86_64
> lvm2-clvm-2.02.177-4.1.x86_64
> lvm2-lockd-2.02.177-4.1.x86_64
> lvm2-2.02.177-4.1.x86_64
> lvm2-testsuite-2.02.177-4.1.x86_64
> 
> tb0307-nd1:/ # pvs
>PV VG  Fmt  Attr PSize  PFree
>/dev/vdb   cluster-vg2 lvm2 a--  40.00g 20.00g
>/dev/vdc   cluster-vg2 lvm2 a--  40.00g 40.00g
> tb0307-nd1:/ # vgs
>VG  #PV #LV #SN Attr   VSize  VFree
>cluster-vg2   2   1   0 wz--nc 79.99g 59.99g
> tb0307-nd1:/ # lvs
>LV  VG  Attr   LSize  Pool Origin Data%  Meta%  Move Log 
> Cpy%Sync Convert
>test-lv cluster-vg2 -wi-ao 20.00g
> tb0307-nd1:/ # pvmove -i 5 /dev/vdb /dev/vdc
>Increasing mirror region size from 0to 16.00 KiB
>Error locking on node a4311a8: Device or resource busy
>Failed to activate cluster-vg2/test-lv   <<== Failed, but in fact, I can 
> mount cluster-vg2/test-lv with ocfs2 file system in the cluster, and 
> read/write files from each node.

Hi


Yep - it's a work in progress - if you take upstream from git - there are 
already fixes committed.  Hopefully next release (2.02.178) will address most 
regressions cause by newer (hopefully better) code.

Do you have a schedule for next release (2.02.178)? pvmove is a good feature, I 
hope we can support it in our next SLE release. 
By the way, some customers really used this feature, but it did not look very 
stable,
especially when users did pvmove during the (clustered) LV is being used for 
reading/writing.
Thanks a lot.
Gang

Good to see someone is really using it...

Regards

Zdenek

___
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/