Bug 1825344
| Summary: | LVM changes to dm_path with respect to VDO create volumes make vdo list show incorrect info | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | bjohnsto |
| Component: | vdo | Assignee: | bjohnsto |
| Status: | CLOSED ERRATA | QA Contact: | Filip Suba <fsuba> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.4 | CC: | awalsh |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.2.3.22 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 02:01:47 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
bjohnsto
2020-04-17 18:32:27 UTC
Here is some output showing the behavior:
[root@localhost ~]# rpm -qa lvm2 device-mapper vdo kmod-kvdo kernel
lvm2-2.03.08-3.el8.x86_64
device-mapper-1.02.169-3.el8.x86_64
kernel-4.18.0-193.8.el8.x86_64
kmod-kvdo-6.2.2.117_8.3-69.el8.x86_64
vdo-6.2.2.117-13.el8.x86_64
[root@localhost ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 20G 0 disk
└─vda1 253:1 0 20G 0 part /
[root@localhost ~]# df -h .
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 20G 2.2G 18G 11% /
[root@localhost ~]# truncate -s 9g loop0
[root@localhost ~]# truncate -s 9g loop1
[root@localhost ~]# losetup loop0 loop0
[root@localhost ~]# losetup loop1 loop1
[root@localhost ~]# vdo create --name vdo0 --device /dev/loop0
Creating VDO vdo0
Logical blocks defaulted to 1569686 blocks.
The VDO volume can address 6 GB in 3 data slabs, each 2 GB.
It can grow to address at most 16 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Starting VDO vdo0
Starting compression on VDO vdo0
VDO instance 0 volume is ready at /dev/mapper/vdo0
[root@localhost ~]# lvcreate -L 8G -V 100G ^C
[root@localhost ~]# vgcreate vg /dev/loop1
Volume group "vg" successfully created
[root@localhost ~]# lvcreate -L 8G -V 100G --type vdo vg/vdopool
The VDO volume can address 5 GB in 10 data slabs, each 512 MB.
It can grow to address at most 4 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Logical volume "lvol0" created.
[root@localhost ~]# vdo list
vdo0
vg-vdopool-vpool
Verified with vdo-6.2.3.114-14.el8.
# vdo create --name vdo0 --device /dev/sda
Creating VDO vdo0
Logical blocks defaulted to 1569686 blocks.
The VDO volume can address 6 GB in 3 data slabs, each 2 GB.
It can grow to address at most 16 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Starting VDO vdo0
Starting compression on VDO vdo0
VDO instance 0 volume is ready at /dev/mapper/vdo0
# vgcreate vg2 /dev/loop2
Physical volume "/dev/loop2" successfully created.
Volume group "vg2" successfully created
# lvcreate -L 8G -V 100G --type vdo vg2/vdopool
The VDO volume can address 4 GB in 2 data slabs, each 2 GB.
It can grow to address at most 16 TB of physical storage in 8192 slabs.
If a larger maximum size might be needed, use bigger slabs.
Logical volume "lvol0" created.
# vdo list
vdo0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (kmod-kvdo bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4551 |