* [linux-lvm] Some questions about the upcoming LVM v2_02_178 @ 2018-06-12 9:01 Gang He 2018-06-12 14:22 ` Joe Thornber 0 siblings, 1 reply; 5+ messages in thread From: Gang He @ 2018-06-12 9:01 UTC (permalink / raw) To: linux-lvm 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 affected? since I saw that clvmd related code has been removed. 3) If clvmd is removed in the next version, which existed features will be affected? 4) What is the next version? v2_02_178 or v3_0_0 ? Thanks Gang ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178 2018-06-12 9:01 [linux-lvm] Some questions about the upcoming LVM v2_02_178 Gang He @ 2018-06-12 14:22 ` Joe Thornber 2018-06-13 2:14 ` Gang He 0 siblings, 1 reply; 5+ messages in thread From: Joe Thornber @ 2018-06-12 14:22 UTC (permalink / raw) To: LVM general discussion and development 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 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. Yes there will be. We've had no bug reports for the -rc, so the final release will be the same as the -rc. > 2) For the next LVM2 version, which components will be affected? since I saw that clvmd related code has been removed. We've decided to bump the version number to 3.0.0 for the release *after* 2.02.178. This change in version number indicates the *start* of some large changes to lvm. Obviously the release notes for v3.0.0 will go into this more. But, initially the most visible changes will be removal of a couple of features: clvmd ----- The locking required to provide this feature was quite pervasive and was restricting the adding of new features (for instance, I'd like to be able to allocate from any LV not just PVs). With Dave Teigland's lvmlockd I think the vast majority of use cases are covered. Those that are wedded to clvmd can continue to use LVM2.02.* Also, testing cluster software is terribly expensive, we just don't have the resources to provide two solutions. lvmapi ------ This library has been deprecated for a while in favour of the dbus api. - Joe ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178 2018-06-12 14:22 ` Joe Thornber @ 2018-06-13 2:14 ` Gang He 2018-06-13 9:43 ` Joe Thornber 0 siblings, 1 reply; 5+ messages in thread From: Gang He @ 2018-06-13 2:14 UTC (permalink / raw) To: linux-lvm Hello Joe, >>> On 2018/6/12 at 22:22, in message <20180612142219.ixpzqxqws3qiwqbm@reti>, Joe Thornber <thornber@redhat.com> 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 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. > > Yes there will be. We've had no bug reports for the -rc, so the final > release will be the same as the -rc. Between LVM2 v2_02_178-rc1 and LVM2 v2_02_177, there will not be any components/features remove, except include some bug fixes, right? Thanks a lot. Gang > >> 2) For the next LVM2 version, which components will be affected? since I saw > that clvmd related code has been removed. > > We've decided to bump the version number to 3.0.0 for the release > *after* 2.02.178. This change in version number indicates the *start* > of some large changes to lvm. > > Obviously the release notes for v3.0.0 will go into this more. But, > initially the most visible changes will be removal of a couple of > features: > > clvmd > ----- > > The locking required to provide this feature was quite pervasive and > was restricting the adding of new features (for instance, I'd like to > be able to allocate from any LV not just PVs). With Dave Teigland's > lvmlockd I think the vast majority of use cases are covered. Those > that are wedded to clvmd can continue to use LVM2.02.* > > Also, testing cluster software is terribly expensive, we just don't > have the resources to provide two solutions. > > lvmapi > ------ > > This library has been deprecated for a while in favour of the dbus api. > > > - Joe > > _______________________________________________ > 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/ ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178 2018-06-13 2:14 ` Gang He @ 2018-06-13 9:43 ` Joe Thornber 2018-06-14 2:14 ` Gang He 0 siblings, 1 reply; 5+ messages in thread From: Joe Thornber @ 2018-06-13 9:43 UTC (permalink / raw) To: LVM general discussion and development On Tue, Jun 12, 2018 at 08:14:17PM -0600, Gang He wrote: > Hello Joe, > > > >>> On 2018/6/12 at 22:22, in message <20180612142219.ixpzqxqws3qiwqbm@reti>, Joe > Thornber <thornber@redhat.com> 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 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. > > > > Yes there will be. We've had no bug reports for the -rc, so the final > > release will be the same as the -rc. > Between LVM2 v2_02_178-rc1 and LVM2 v2_02_177, > there will not be any components/features remove, except include some bug fixes, right? 178 dropped support for two very old metadata formats (pool and lvm1), and switched to async io all io ops apart from logging. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [linux-lvm] Some questions about the upcoming LVM v2_02_178 2018-06-13 9:43 ` Joe Thornber @ 2018-06-14 2:14 ` Gang He 0 siblings, 0 replies; 5+ messages in thread From: Gang He @ 2018-06-14 2:14 UTC (permalink / raw) To: linux-lvm Hello Joe, Thank for your patient explaining, very useful. -Gang >>> On 2018/6/13 at 17:43, in message <20180613094303.53zhqymzojhr5dsx@reti>, Joe Thornber <thornber@redhat.com> wrote: > On Tue, Jun 12, 2018 at 08:14:17PM -0600, Gang He wrote: >> Hello Joe, >> >> >> >>> On 2018/6/12 at 22:22, in message <20180612142219.ixpzqxqws3qiwqbm@reti>, Joe >> Thornber <thornber@redhat.com> 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 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. >> > >> > Yes there will be. We've had no bug reports for the -rc, so the final >> > release will be the same as the -rc. >> Between LVM2 v2_02_178-rc1 and LVM2 v2_02_177, >> there will not be any components/features remove, except include some bug > fixes, right? > > > 178 dropped support for two very old metadata formats (pool and lvm1), and > switched > to async io all io ops apart from logging. > > _______________________________________________ > 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/ ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2018-06-14 2:14 UTC | newest] Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-06-12 9:01 [linux-lvm] Some questions about the upcoming LVM v2_02_178 Gang He 2018-06-12 14:22 ` Joe Thornber 2018-06-13 2:14 ` Gang He 2018-06-13 9:43 ` Joe Thornber 2018-06-14 2:14 ` Gang He
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).