Hi David,
On 2020/11/19 2:23, David Teigland wrote:
On Wed, Nov 18, 2020 at 09:28:21AM +0800, Gang He wrote:
I prefer to use a metadata flag for each VG or LV to skip auto-activation.
Otherwise, it is not easy for the pacemaker cluster to manager a local
VG(e.g. local or systemid type) in a
On 11/18/2020 12:17 AM, David Teigland wrote:
On Tue, Nov 17, 2020 at 04:00:10PM +0800, heming.z...@suse.com wrote:
Hello LVM-maintainers,
Currently activation/auto_activation_volume_list is not enable and it does the
default behavior:
pvscan will activate all the devices on booting.
Th
Hi David,
Thank for your helps.
On 9/29/2020 10:02 PM, David Teigland wrote:
On Tue, Sep 29, 2020 at 08:46:25AM +, Gang He wrote:
ghe-tw-nd1# lvresize -L+1024M vg1/lv1
WARNING: extending LV with a shared lock, other hosts may require LV refresh.
Size of logical volume vg1/lv1
Hello List,
I am using lvm2 v2.03.10(or v2.03.05), I setup a lvm2-lockd based (three nodes)
cluster.
I created PV, VG and LV, formated LV with a cluster file system (e.g. ocfs2).
So far, all the things work well, I can write the files from each node.
Next, I extended the online LV from node1, e.g
Hi David,
Thank for your reply.
more questions,
On 7/9/2020 12:05 AM, David Teigland wrote:
On Wed, Jul 08, 2020 at 03:55:55AM +, Gang He wrote:
but I cannot do online LV reduce from one node,
the workaround is to switch VG activation_mode to exclusive, run lvreduce
command on the node
Hello List,
I use lvm2-2.03.05, I am looking at online pvmove/lvresize on shared VG, since
there are some problems in old code.
Now, I setup three node cluster, and one shared VG/LV, and a cluster file
system on top of LV.
e.g.
primitive ocfs2-2 Filesystem \
params device="/dev/vg1/lv1" director
Hi David,
I did some testing with this patch.
It looks OK. Do you plan to commit the patch into the git tree?
Thanks
Gang
> -Original Message-
> From: David Teigland [mailto:teigl...@redhat.com]
> Sent: 2020年4月27日 23:04
> To: Gang He
> Cc: LVM general discussion
Hello List,
In libdlm code, cluster_ringid_seq variable is defined with uint32_t in
dlm_controld/dlm_daemon.h,
the corosync API returns uinit64_t ring_id, in the current code, we use type
cast to get the low-32bit ring-id.
But, in some case, the corosync returns a huge ring-id (greater than 32bi
Hi Guys,
Sometimes we encountered some lvm2 meta-data damage (by lvm2 commands) problems.
Do we have a way to clone (or dump) the customer lvm2 environment? such like
file system e2image tool.
for example, we can dump each pv(meta data + data(with file hole)) to a file,
next we can rebuild the c
ehalf Of Alasdair G Kergon
> Sent: 2019年10月14日 21:20
> To: LVM general discussion and development
> Subject: Re: [linux-lvm] devices/dir configuration option in /etc/lvm/lvm.conf
> can be edited?
>
> On Mon, Oct 14, 2019 at 10:52:02AM +, Gang He wrote:
> > That means we sho
general discussion and development ; Gang
> He
> Subject: Re: devices/dir configuration option in /etc/lvm/lvm.conf can be
> edited?
>
> Dne 14. 10. 19 v 10:00 Gang He napsal(a):
> > Hello List,
> >
> > By default, devices/dir configuration option in /et
Hello List,
By default, devices/dir configuration option in /etc/lvm/lvm.conf is "=/dev".
But, if I edit this configuration option, e.g. dir = "/dev/lvm", then lvcreate
command will fail.
sles12sp4-node:/dev # lvcreate -L2G -ay -n testlv vgdata
/dev/lvm/vgdata/testlv: not found: device not cle
David Teigland [mailto:teigl...@redhat.com]
> Sent: 2019年10月11日 23:14
> To: Heming Zhao
> Cc: linux-lvm@redhat.com; Gang He
> Subject: Re: [linux-lvm] pvresize will cause a meta-data corruption with error
> message "Error writing device at 4096 length 512"
>
> On
Hello List,
When I tried to upgrade libdlm to v4.0.9, I can see one commit for add TCP
multihoming/failover support.
commit 7a273b8714da400d292d6c9762acedcde1997e52
Author: David Windsor
Date: Tue May 7 09:56:53 2019 -0400
dlm_controld: bind to all interfaces for failover
According to t
Hi Ingo and Ilia,
Thank for your helps.
> -Original Message-
> From: Ingo Franzki [mailto:ifran...@linux.ibm.com]
> Sent: 2019年9月11日 18:11
> To: Ilia Zykov ; LVM general discussion and development
> ; Gang He
> Subject: Re: [linux-lvm] pvresize will cause a meta-da
Hello List,
Our user encountered a meta-data corruption problem, when run pvresize command
after upgrading to LVM2 v2.02.180 from v2.02.120.
The details are as below,
we have following environment:
- Storage: HP XP7 (SAN) - LUN's are presented to ESX via RDM
- VMWare ESXi 6.5
- SLES 12 SP 4 Gues
-ball file name format looks changed.
So, which link is the official dlm release download link?
Thanks
Gang
> -Original Message-
> From: David Teigland [mailto:teigl...@redhat.com]
> Sent: 2019年8月8日 1:05
> To: Gang He
> Cc: LVM general discussion and development
> S
Hi David,
Today, I downloaded the dlm user-space tool source code tar-ball from
https://pagure.io/dlm.
I found the tar-ball name format has been changed to dlm-dlm-4.0.x.tar.gz, the
newly added "dlm-" prefix name is on purpose?
Thanks
Gang
___
linu
月10日 20:48
To: LVM general discussion and development ; Gang He
Subject: Re: [linux-lvm] Which lvm2 code branches are important?
On 7/10/19 8:42 AM, Gang He wrote:
> Hello List,
>
> After you clone the code from git://sourceware.org/git/lvm2.git, you can find
> lots of remote c
Hello List,
After you clone the code from git://sourceware.org/git/lvm2.git, you can find
lots of remote code branches.
But which code branches are important for the third party users/ developer?
That means we should monitor these code branches.
For example,
Which code branches are main (or lon
Hi Marian,
Thank for your helps, the patch is effective to fix this error message.
Thanks
Gang
-Original Message-
From: Marian Csontos [mailto:mcson...@redhat.com]
Sent: 2019年7月8日 16:37
To: LVM general discussion and development ; Gang He
Subject: Re: [linux-lvm] "Unknown featu
Hi Guys,
I uses lvm2-2.02.180, I got an error message when running lvs/lvdisplay against
cached LVs.
e.g.
linux-v5ay:~ # lvs
Unknown feature in status: 8 1324/8192 128 341/654272 129 151 225 1644 0 341
0 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0
rw -
LV
...@redhat.com]
Sent: 2019年7月1日 18:23
To: LVM general discussion and development ; Gang He
Subject: Re: Can't remove the snap LV of root volume on multipath disk PV
Dne 01. 07. 19 v 8:31 Gang He napsal(a):
> Hello List,
>
> I am using lvm2-2.02.180 on SLES12SP4, I cannot remove the s
Hello List,
I am using lvm2-2.02.180 on SLES12SP4, I cannot remove the snap LV of root
volume, which is based on multipath disk PV.
e.g.
linux-kkay:/ # lvremove /dev/system/snap_root
WARNING: Reading VG system from disk because lvmetad metadata is invalid.
Do you really want to remove active l
Hello Guys,
Any ideas? or what information do I need to provide to help this problem?
Thanks a lot.
Gang
>>> On 2019/6/19 at 17:26, in message
<5d09ffc902f90006d...@prv1-mh.provo.novell.com>, "Gang He"
wrote:
> Hello List,
>
> Our user is using lvm2-
Hello List,
Our user is using lvm2-2.02.180, he attempted to remove a snapshot LV, but
failed with the below error,
lvremove /dev/evg00/snap_var
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Do you really want to remove active logical volume evg00/snap_var? [y/n]: y
Hello Guys,
I found lvconvert command (in lvm lvm2-2.02.120) did not handle "--stripes"
option correctly.
The reproduce steps are as below,
# vgcreate vgtest /dev/vdb /dev/vdc /dev/vdd /dev/vde /dev/vdf /dev/vdg
# lvcreate -n lvtest -L 8G vgtest
# lvconvert --mirrors 1 --stripes 3 vgtest/lvtest
#
t;> On 2019/5/14 at 16:00, in message
<59ef89f8-9642-4455-cef0-450816eac...@redhat.com>, Zdenek Kabelac
wrote:
> Dne 14. 05. 19 v 8:25 Gang He napsal(a):
>> Hello Guys,
>>
>> Anybody touched this area?
>>
>> Thanks
>> Gang
>
>
> Hi
>
&
Hello Guys,
Anybody touched this area?
Thanks
Gang
>>> On 2019/5/10 at 11:00, in message
<5cd4e95002f900064...@prv1-mh.provo.novell.com>, "Gang He"
wrote:
> Hello List,
>
> Our build team wants to build LVM2 with LTO enablement, but looks failed.
>
Hello List,
Our build team wants to build LVM2 with LTO enablement, but looks failed.
The error message likes,
[ 30s] gcc -fmessage-length=0 -grecord-gcc-switches -O2 -Wall
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection -flto
ache has no info for vgname "#orphans".
#locking/locking.c:331 Dropping cache for #orphans.
Thanks
Gang
>>> On 4/24/2019 at 11:08 pm, in message <20190424150858.ga3...@redhat.com>,
>>> David
Teigland wrote:
> On Tue, Apr 23, 2019 at 09:23:29PM -0600,
23:24, in message
<9cd91b48-408b-f7a9-c4bc-df05d5537...@redhat.com>, Peter Rajnoha
wrote:
> On 4/23/19 7:15 AM, Gang He wrote:
>> Hello List,
>>
>> One user complained this error message.
>> The user has a usb sd card reader with no media present. When they issue
Hello List,
One user complained this error message.
The user has a usb sd card reader with no media present. When they issue a
pvscan under lvm2-2.02.180 the device is opened which results in 'No medium
found' being reported.
But lvm2-2.02.120 did not do this (the device appears to get filtere
Hello Guys,
I create a md device with a big minor number, and add this md device as PV disk.
Then, pvdisplay can not display this PV.
But, if I disable lvmetad via changing the configuration setting "use_lvmetad =
1" to "use_lvmetad = 0",
pvdisplay can display this PV, then I can do the next thin
Hello List,
As you know, in the past versions(e.g. v2.02.120), lvcreate supports creating a
mirror type LV with "--mirrorlog mirrored" option,
But in the latest versions(e.g. v2.02.180), lvm2 says "mirrored is a persistent
log that is itself mirrored, but should be avoided. Instead, use the rai
Hello List,
As you know, in the past versions(e.g. v2.02.120), lvcreate supports
creating a mirror type LV with "--mirrorlog mirrored" option,
But in the latest versions(e.g. v2.02.180), lvm2 says "mirrored is a
persistent log that is itself mirrored, but should be avoided. Instead, use
the raid1
Hello David,
I am sorry, I can not understand your reply quickly.
>>> On 2018/10/23 at 23:04, in message <20181023150436.gb8...@redhat.com>, David
Teigland wrote:
> On Mon, Oct 22, 2018 at 08:19:57PM -0600, Gang He wrote:
>> Process: 815 ExecStart=/usr/sbin/lvm pvscan
Hello Guys,
Did you see this problem before?
it looks there was a similar problem from the Redhat website
https://access.redhat.com/solutions/1421123#.
Thanks
Gang
>>> On 2018/10/19 at 17:05, in message
<5bc99e5602f90003b...@prv1-mh.provo.novell.com>, "Gang He&q
0181018175923.gc28...@redhat.com>, David
Teigland wrote:
> On Thu, Oct 18, 2018 at 11:01:59AM -0500, David Teigland wrote:
>> On Thu, Oct 18, 2018 at 02:51:05AM -0600, Gang He wrote:
>> > If I include this patch in lvm2 v2.02.180,
>> > LVM2 can activate LVs
Hello List,
I got a bug report from the customer, which said the node was fenced in the
cluster when they enabled cmirrord.
Before the node was fenced, we can see some log printed as below,
2018-09-25T12:55:26.555018+02:00 qu1ci11 cmirrord[6253]: cpg_mcast_joined
error: 2
2018-09-25T12:55:31.60
t 18, 2018 at 02:51:05AM -0600, Gang He wrote:
>> > If I include this patch in lvm2 v2.02.180,
>> > LVM2 can activate LVs on the top of RAID1 automatically? or we still have
> to set "allow_changes_with_duplicate_pvs=1" in lvm.conf?
>>
>> I didn't nee
Hello David,
Thank for your help.
If I include this patch in lvm2 v2.02.180,
LVM2 can activate LVs on the top of RAID1 automatically? or we still have to
set "allow_changes_with_duplicate_pvs=1" in lvm.conf?
Thanks
Gang
>>> On 2018/10/18 at 2:42, in message <20181017184204.gc14...@redhat.com>
Hello David,
>>> On 2018/10/15 at 23:26, in message <20181015152648.gb29...@redhat.com>,
>>> David
Teigland wrote:
> On Sun, Oct 14, 2018 at 11:39:20PM -0600, Gang He wrote:
>> >> [ 147.371698] linux-472a dracut-initqueue[391]: Cannot activate LVs in
&g
Hell David,
>>> On 2018/10/8 at 23:00, in message <20181008150016.gb21...@redhat.com>, David
Teigland wrote:
> On Mon, Oct 08, 2018 at 04:23:27AM -0600, Gang He wrote:
>> Hello List
>>
>> The system uses lvm based on raid1.
>> It seems that the PV of t
Hello List
The system uses lvm based on raid1.
It seems that the PV of the raid1 is found also on the single disks that build
the raid1 device:
[ 147.121725] linux-472a dracut-initqueue[391]: WARNING: PV
qG1QRz-Ivm1-QVwq-uaHV-va9w-wwXh-lIIOhV on /dev/sda2 was already found on
/dev/md1.
[ 147
Hello List,
I use a old version LVM2 2.02.98 on kernel 3.0.101, I encountered such a
problem.
The detailed steps are as below,
I am doing an update with the following strategy for updates
make LVM Snapshot of root ("/") file system partition
Run zypper updates ->
Run a script to check certain
Hello List,
I am using LVM2 v2.02.180 in a clvmd based cluster (three nodes), but sometimes
I encountered lvm2 command hang problem.
When the comand is hanged, all lvm2 related commands from each node will be
hanged.
For example,
First command was hanged at node 2,
sle12sp4b2-nd2:/ # pvmove -i 5
Hello Marian,
Thank for your explanation, it's very helpful to me.
Thanks
Gang
>>> On 2018/8/3 at 22:05, in message
, Marian Csontos
wrote:
> On 08/03/2018 11:40 AM, Gang He wrote:
>> Hello List,
>>
>> I want to upgrade LVM2/CLVM to v2.02.180 from v2.02.
Hello List,
I want to upgrade LVM2/CLVM to v2.02.180 from v2.02.120, but there are some
problems which I want to confirm with you guys.
1) How to migrate /etc/lvm/lvm.conf? since the existing configuration file does
not include some new attributes,
could you help to figure out which new key att
Hello List,
I encountered a problem with the source code 2.02.178,
vgchange command did not activate mirrored LV in VG, the error messages were as
below,
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:01 1024M 0 rom
vda254:00 40G 0 disk
├─vda1 254:104G 0 part [S
Hello List,
For LVM2 for v2_02_178, there is a file python_lvm_unit.py.in under
/lvm2/test/api.
in this file, the first line looks like "#!@PYTHON@", I do not know if we
should replace this line with "#!/usr/bin/python3"?
Otherwise, there will be a building error, the building log is as below fo
Hello Joe,
Thank for your patient explaining, very useful.
-Gang
>>> On 2018/6/13 at 17:43, in message <20180613094303.53zhqymzojhr5dsx@reti>,
>>> Joe
Thornber wrote:
> On Tue, Jun 12, 2018 at 08:14:17PM -0600, Gang He wrote:
>> Hello Joe,
>>
>&
Hello Joe,
>>> On 2018/6/12 at 22:22, in message <20180612142219.ixpzqxqws3qiwqbm@reti>,
>>> Joe
Thornber wrote:
> On Tue, Jun 12, 2018 at 03:01:27AM -0600, Gang He wrote:
>> Hello List,
>>
>> I saw there was a tag "v2_02_178-rc1" for
Hello List,
I saw there was a tag "v2_02_178-rc1" for LVM2, then I have some questions
about the upcoming LVM v2_02_178.
1) Will there be the version v2_02_178 for LVM2? since I saw some text about
Version 3.0.0 in the git change logs.
2) For the next LVM2 version, which components will be aff
Hi Martion,
>>> On 2018/6/11 at 21:20, in message
, Marian Csontos
wrote:
> On 06/11/2018 08:13 AM, Gang He wrote:
>> Hi Martian,
>>
>>>>> On 2018/5/30 at 18:37, in message
>> <2397dd2b-deef-2bf2-47ca-51fb6f880...@redhat.com>, Marian Csontos
&
Hi Martian,
>>> On 2018/5/30 at 18:37, in message
<2397dd2b-deef-2bf2-47ca-51fb6f880...@redhat.com>, Marian Csontos
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
Ok, I will try.
Thanks
Gang
>>> On 5/30/2018 at 10:12 pm, in message
, Zdenek Kabelac
wrote:
> Dne 30.5.2018 v 11:23 Gang He napsal(a):
>> Hello List,
>>
>> As you know, I ever reported that lvcreate could not create a mirrored LV,
> the root cause is a
Hi Marian,
Thank for your explanation, I will try 2.02.178.
Thanks
Gang
>>> On 5/30/2018 at 6:42 pm, in message
<80318f1a-2b2e-9d0f-ae16-3b1eb0af2...@redhat.com>, Marian Csontos
wrote:
> On 05/25/2018 09:45 AM, Gang He wrote:
>> Hello Joe,
>>
>> When will
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
Hi Zdenek,
>>> Zdenek Kabelac 2018/5/25 16:14 >>>
Dne 25.5.2018 v 09:37 Gang He napsal(a):
> Hello List,
>
> I am using lvm version 2.02.177(2), tried to create a mirrored LV, but failed
> with the errors,
> tb0307-nd1:~ # pvs
>PV VG
Hello Joe,
When will the formal LVM 2.02.178 be released?
In LVM2.02.178, online pvmove can work well under the cluster environment?
Thanks
Gang
>>> Joe Thornber 2018/5/25 15:03 >>>
ftp://sources.redhat.com/pub/lvm2/LVM2.2.02.178-rc1.tgz
Version 2.02.178
There are going to
Hello List,
I am using lvm version 2.02.177(2), tried to create a mirrored LV, but failed
with the errors,
tb0307-nd1:~ # pvs
PV VG Fmt Attr PSize PFree
/dev/vdb cluster-vg2 lvm2 a-- 40.00g 36.00g
/dev/vdc cluster-vg2 lvm2 a-- 40.00g 40.00g
tb0307-nd1:~ # vgs
VG
Hi Zdenek and Guys,
As you know, we prefer to consider this problem as mis-operation.
But, the customer want to know if we should add a warning in this case?
Any comments for this customer's request?
Thanks
Gang
>>> Zdenek Kabelac 2018/3/26 18:46 >>>
Dne 26.3.2018 v
Hello Zdenek,
Thank for your reply.
As you said some days ago, you will release LVM 2.02.178,
which will be a stable version? include some PVmove bug fixes?
Thanks
Gang
>>>
> Dne 26.4.2018 v 04:07 Gang He napsal(a):
>> Hello Zdenek,
>>
>> Do you remember LVM fo
Hello Zdenek,
Do you remember LVM for this version supports PVmove, or not?
Since there is a user which is pinging this question.
Thanks
Gang
>>>
> Hello List,
>
> This is another pvmove problem, the LVM version is 2.02.120(2) (2015-05-15).
> This bug can be reproduced (not each time, but ver
Hello List,
This is another pvmove problem, the LVM version is 2.02.120(2) (2015-05-15).
This bug can be reproduced (not each time, but very easy),
the problem is, online pvmove brings the upper file system hang.
the environment is a three-node cluster (CLVM+OCFS2).
1) create two PV, create one VG
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 t
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 /
I can compile the code smoothly on openSUSE Tumbleweed, but I am not sure if my
configuration is the same with yours.
tb0307-nd3:/usr/src/packages/BUILD/LVM2.2.02.177 # rpm -qa | grep -i san
sane-backends-1.0.27-3.3.x86_64
noto-sans-fonts-20170919-2.1.noarch
adobe-sourcesanspro-fonts-2.020-1.8.no
Hi Zdenek,
>>>
> Dne 27.3.2018 v 07:55 Gang He napsal(a):
>> Hi Fran,
>>
>>
>>>>>
>>> On 26 March 2018 at 08:04, Gang He wrote:
>>>> It looks like each PV includes a copy meta data for VG, but if some PV has
>>> chang
Hi Fran,
>>>
> On 26 March 2018 at 08:04, Gang He wrote:
>> It looks like each PV includes a copy meta data for VG, but if some PV has
> changed (e.g. removed, or moved to another VG),
>> the remained PV should have a method to check the integrity when each
>
Hi Xen,
>>>
> Gang He schreef op 23-03-2018 9:30:
>
>> 6) attach disk2 to VM2(tb0307-nd2), the vg on VM2 looks abnormal.
>> tb0307-nd2:~ # pvs
>> WARNING: Device for PV JJOL4H-kc0j-jyTD-LDwl-71FZ-dHKM-YoFtNV not
>> found or rejected by a filter.
>
Hello List,
Since I am new to LVM area, but I got a problem about LVM can't work normally
after attaching disk volumes originally in a VG on another machine.
Then, I sent this problem to the list, to see if we can get a fix or there has
been a fix.
The problem is very easy to reproduce,
1) creat
73 matches
Mail list logo
