Discussion:
[linux-lvm] Some questions about the upcoming LVM v2_02_178
Gang He
2018-06-12 09:01:27 UTC
Permalink
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
Joe Thornber
2018-06-12 14:22:20 UTC
Permalink
Post by Gang He
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.
Post by Gang He
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
Gang He
2018-06-13 02:14:17 UTC
Permalink
Hello Joe,
Post by Gang He
Post by Gang He
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.
Post by Gang He
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
Post by Gang He
Post by Gang He
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
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
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Joe Thornber
2018-06-13 09:43:03 UTC
Permalink
Post by Gang He
Hello Joe,
Post by Gang He
Post by Gang He
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.
Post by Gang He
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.
Gang He
2018-06-14 02:14:30 UTC
Permalink
Hello Joe,

Thank for your patient explaining, very useful.

-Gang
Post by Gang He
Post by Gang He
Hello Joe,
Post by Gang He
Post by Gang He
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.
Post by Gang He
1) Will there be the version v2_02_178 for LVM2? since I saw some text
about
Post by Gang He
Post by Gang He
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
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
Loading...