Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCorey Marthaler
2017-11-13 16:45:30 UTC
Description of problem:
The underlying volume the VDO is being created on is 10G.
[root@mckinley-04 ~]# lvs -a /dev/snapper_thinp/origin
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
origin snapper_thinp Vwi-a-t--- 10.00g POOL 1.41
# Shouldn't the created Logical size be either 20G, or a warning printed that the supplied 20G option wont work?
[root@mckinley-04 ~]# vdo create --name virt_vdovolume --vdoLogicalSize 20G --device /dev/snapper_thinp/origin
Creating VDO virt_vdovolume
Starting VDO virt_vdovolume
Starting compression on VDO virt_vdovolume
VDO instance 31 volume is ready at /dev/mapper/virt_vdovolume
[root@mckinley-04 ~]# vdo status | grep " size"
Logical size: 10G
Physical size: 10G
Version-Release number of selected component (if applicable):
vdo-6.1.0.34-8 BUILT: Fri Nov 3 06:58:45 CDT 2017
kmod-kvdo-6.1.0.34-7.el7 BUILT: Fri Nov 3 06:44:06 CDT 2017
This is actually a duplicate of BZ 1510558. It's not a case of the "--vdoLogicalSize" option being ignored, but the previous metadata is on disk, because the "vdoformat" command didn't actually run.
*** This bug has been marked as a duplicate of bug 1510558 ***
Description of problem: The underlying volume the VDO is being created on is 10G. [root@mckinley-04 ~]# lvs -a /dev/snapper_thinp/origin LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert origin snapper_thinp Vwi-a-t--- 10.00g POOL 1.41 # Shouldn't the created Logical size be either 20G, or a warning printed that the supplied 20G option wont work? [root@mckinley-04 ~]# vdo create --name virt_vdovolume --vdoLogicalSize 20G --device /dev/snapper_thinp/origin Creating VDO virt_vdovolume Starting VDO virt_vdovolume Starting compression on VDO virt_vdovolume VDO instance 31 volume is ready at /dev/mapper/virt_vdovolume [root@mckinley-04 ~]# vdo status | grep " size" Logical size: 10G Physical size: 10G Version-Release number of selected component (if applicable): vdo-6.1.0.34-8 BUILT: Fri Nov 3 06:58:45 CDT 2017 kmod-kvdo-6.1.0.34-7.el7 BUILT: Fri Nov 3 06:44:06 CDT 2017