From: "Gang He" <ghe@suse.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] PVmove can not work on lvm2-2.02.177
Date: Wed, 04 Apr 2018 01:12:39 -0600 [thread overview]
Message-ID: <5AC47AE7020000F9001CAC9D@prv-mh.provo.novell.com> (raw)
In-Reply-To: <bdd19fc5-b0ff-4463-2bab-c3768d3d4a1e@redhat.com>
Hi Zdenek,
>>> Zdenek Kabelac <zkabelac@redhat.com> 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 0 to 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@http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2018-04-04 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 2:28 [linux-lvm] PVmove can not work on lvm2-2.02.177 Gang He
2018-04-03 8:10 ` Zdenek Kabelac
2018-04-04 7:12 ` Gang He [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=5AC47AE7020000F9001CAC9D@prv-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).