Re: [linux-lvm] Which lvm2 code branches are important?
Hello Marian, Thank for your reply. About the detailed changes for V2.03, where do we can find the related documents from the external link? Thanks Gang -Original Message- From: linux-lvm-boun...@redhat.com [mailto:linux-lvm-boun...@redhat.com] On Behalf Of Marian Csontos Sent: 2019年7月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 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 long-active) code branches? > Which code branches are used for which lvm2 products (big versions)? master - 2.03 branch, new features land here, stable-2.02 - legacy 2.02 branch, bug fixes mostly. > What are the main differences between different lvm2 products? E.g. some > features are added/removed. 2.03 vs 2.03: - dropped lvmetad and clvmd, - added handling of writecache and VDO targets. > > > Thanks a lot. > 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/ ___ 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] lvdisplay "open" field computing
Dne 10. 07. 19 v 13:54 Simon ELBAZ napsal(a): Hi Zdenek, Thanks for your feedback. The kernel version is: [root@panoramix ~]# uname -a Linux panoramix.ch-perrens.fr 2.6.32-573.12.1.el6.x86_64 #1 SMP Tue Dec 15 21:19:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Hi So this is really a very historical kernel - released ~10 years back. I'm afraid none is going to look out for the reasoning of any kernel bug It might be interesting to see if you get any reproducer to give you hints how to avoid this happen (at least not easily). Jul 2 03:08:10 panoramix LVM(pri_ISCSIVG0_vg_obm)[18618]: INFO: Retry deactivating volume group vg_obm This is why I am trying to understand how the field is computed. Simple rule applied here: DM devices in use (open_count > 0) cannot be deactivated. Occasionally there were 'race events' with udev - where device which should have been otherwise unused has been asynchronously opened by udev scanning rules - but that's like is not your case. As you seems to have device open count higher permanently - So if you are sure there is no running 'APP' after umount, that keeps device open - it could be likely be some very old bug in kernel with very high probably 99.9% of being fixed ;) 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/
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 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 long-active) code branches? Which code branches are used for which lvm2 products (big versions)? master - 2.03 branch, new features land here, stable-2.02 - legacy 2.02 branch, bug fixes mostly. What are the main differences between different lvm2 products? E.g. some features are added/removed. 2.03 vs 2.03: - dropped lvmetad and clvmd, - added handling of writecache and VDO targets. Thanks a lot. 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/
Re: [linux-lvm] lvdisplay "open" field computing
Dne 10. 07. 19 v 9:13 Simon ELBAZ napsal(a): Hi, This LV seems mounted on single mountpoint. The lsof output is: Hmm Which kernel version is this - aren't we tracking issue for some ancient kernel ? Why have you actually started to hunt the reason for opencount 2 ? Has the machine experienced some troubles ? Aren't there some namespaces in use - so i.e. volume is used in different namespace ?? grep 253:3 /proc/*/mountinfo - showing something unusual ? 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/
Re: [linux-lvm] lvdisplay "open" field computing
Thanks for your answer. From your explanation, open=2 should '"normally" not happen ? Regards Simon On 09/07/2019 17:06, Zdenek Kabelac wrote: Dne 09. 07. 19 v 11:47 Simon ELBAZ napsal(a): Hi, I am trying to understand how the open field is computed. On a CentOS6 server, lvdisplay has the following output: /lvdisplay /dev/mapper/vg_obm-var_spool_imap // // --- Logical volume ---// // LV Path /dev/vg_obm/var_spool_imap// // LV Name var_spool_imap// // VG Name vg_obm// // LV UUID 0oK7h0-tDZH-eUxE-AyBw-cK7x-U9pS-W7X4Uh// // LV Write Access read/write// // LV Creation host, time panoramix.ch-perrens.fr, 2015-01-16 11:03:10 +0100// // LV Status available// // # open 2// // LV Size 1,92 TiB// // Current LE 504572// // Segments 2// // Allocation inherit// // Read ahead sectors auto// // - currently set to 256// // Block device 253:3// / And dmsetup show the following info: /# dmsetup info -c | grep "253" | grep " 3"// //vg_obm-var_spool_imap 253 3 L--w 2 2 0 LVM-1i1v6pEjab2WslaDQRvkf8eLk6QfBW4J0oK7h0tDZHeUxEAyBwcK7xU9pSW7X4Uh/ Could you please give me some hint to understand how "open = 2" is obtained ? Hi Open field is counted in DM driver. Whenever device is opened - +1 - closed -1. You should be able to check 'lsof' to check and see if there are any userspace openners. But you will not see 'kernel' opens this ways. So i.e. if you mount DM device - it should be 1 open. Occasionally you can hit some bug in target drivers - then counters can go crazy and become confusing - then your solution is to collect as much info as possible - and reboot 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] Which lvm2 code branches are important?
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 long-active) code branches? Which code branches are used for which lvm2 products (big versions)? What are the main differences between different lvm2 products? E.g. some features are added/removed. Thanks a lot. 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/
Re: [linux-lvm] "Unknown feature in status" message when running lvs/lvdisplay against cached LVs
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 feature in status" message when running lvs/lvdisplay against cached LVs On 7/5/19 11:20 AM, Gang He wrote: > 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 VG Attr LSize Pool Origin Data% Meta% Move > Log Cpy%Sync Convert >home system -wi-ao 17.99g >root system Cwi-aoC--- 20.00g [lvc_root] [root_corig] 0.05 16.16 > 0.00 >swap system -wi-ao 2.00g You need this patch: https://sourceware.org/git/?p=lvm2.git;a=commit;h=adf9bf80a32500b45b37eb24b98fa7c2c933019e Kernel introduced a new feature which is not recognized by lvm versions released before the kernel (which is anything up to latest 2.02.185). This will be included in the next lvm release. -- Marian > > The bug can be reproduced stably with the below steps. > Have a (virtual) machine with 2 disk drives Install os with LVM as > root volume Then, add the second disk after os is installed. > # pvcreate /dev/sdb > # vgextend system /dev/sdb > # lvcreate --type cache-pool -l 100%FREE -n lvc_root system /dev/sdb # > lvconvert --type cache --cachepool system/lvc_root system/root then > run `lvs` or `lvdisplay` command to trigger the issue > > > 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/
