You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://github.com/dm-vdo/vdo-devel is where most of our work is developed. It will continue to be active for the forseeable future. This repository is upstream of the kernel module code that gets sent to the Linux kernel, and it is also upstream of our userspace tool releases.
https://github.com/dm-vdo/kvdo is currently used only for kernel modules supporting older (el8 or el9) kernels. On newer kernels (6.9+), you can ignore this repository and use the dm-vdo module in the kernel instead. These branches are not under active development and will only be updated sporadically as we fix bugs. We do monitor this repo for issue reports, though.
https://github.com/dm-vdo/vdo will continue to be active as the place where we publish our userspace tools. The 8.3.x versions are the most recent and will be updated to be compatible with the in-kernel dm-vdo module. We also monitor this reposiotry for issue reports.
For support, the best places to ask are either in this repository (vdo-devel) or on the dm-devel mailing list upstream. We will generally respond to issues in any repository, but it might take us a little longer to notice issues filed in the kvdo or vdo repositories.
Documentation is a little trickier. The RHEL 9 documentation is probably the most comprehensive, and I know there is currently work to update it. "man lvmvdo" and "man lvm" are fairly good but to me they look somewhat out-of-date. I believe there is active work in lvm to improve the lvm-vdo integration, but the documentation may lag for a bit while those features are worked out. You can always ask questions here if you want to check or clarify anything.
One more think to keep in mind: lvm2 is the recommended tool to manage vdo volumes, but in order to properly use the dm-vdo module built into the kernel, you will need to have lvm2-2.03.23 or later. Make sure your lvm2 package is up-to-date, especially since improvements are being actively made in this space right now.
Hello guys, it's been a while !
Very well done for kernel merge, it will be a game changer !
Now, can you tell us :
The text was updated successfully, but these errors were encountered: