As part of the rebase and efforts to get VDO included upstream into the
mainline kernel, we joined the two kernel modules (previously kvdo and uds)
into a single module now named 'kvdo'.
- Resolves: rhbz#2071648
Signed-off-by: Andrew Walsh <awalsh@redhat.com>
Creating partitions on top of loopback devices stopped working and it is
failing due to a reason that is unrelated to this package. Previously
partition-based testing was established to ensure that the VDO-manager based
VDO could handle things appropriately, but now that we're based on LVM, which
is more mature in this region, we can trust that this is being tested
appropriately elsewhere.
Resolves: rhbz#2095768
Signed-off-by: Andrew Walsh <awalsh@redhat.com>
- Fixed vdostats output issues.
Resolves: rhbz#2004576
- Removed incorrect assumptions about major device numbers in vdostats.
Resolves: rhbz#2045885
- Made improvements to the vdorecover script.
Resolves: rhbz#2047543
- Added a tool to make LVMVDO pools read/write so that support and debugging tools may access them.
Resolves: rhbz#2047543
Signed-off-by: Andrew Walsh <awalsh@redhat.com>
Fixed up gating test to accommodate the removal of python-based VDO Manager.
- Related: rhbz#1949159
Rebased to upstream candidate.
- Resolves: rhbz#1955374
Removed all python based tools, and all management should now be done with
LVM.
- Resolves: rhbz#1949159
vdostats is now a C program
- Resolves: rhbz#1972302