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.
Description of problem:
vdo create --vdoSlabSize=0 seems to use defautl slab size (2G), but there is no mention about it in manpage or help.
manpage:
--vdoSlabSize=megabytes
Specifies the size of the increment by which a VDO is grown. Using a smaller size constrains the total maximum physical size that can be accommodated. Must be a power of two between 128M and 32G. Using a value with a S (sectors), B (bytes), K (kilo‐bytes), M (megabytes), G (gigabytes), T (terabytes), P (petabytes) or E (exabytes) suffix is optional. If no suffix is used, the value will be interpreted as megabytes. The default is 2G.
--help:
--vdoSlabSize <megabytes>
Specifies the size of the increment by which a VDO is
grown. Using a smaller size constrains the total
maximum physical size that can be accommodated. Must
be a power of two between 128M and 32G; the default is
2G. Using a value with a S(ectors), B(ytes),
K(ilobytes), M(egabytes), G(igabytes), T(erabytes),
P(etabytes) or E(xabytes) suffix is optional. If no
suffix is used, the value will be interpreted as
megabytes.
Note: Some values allow using '0' as default, but I cannot see the merit in it. imho it just gives some confusion and makes the manpage unnecessary longer.
Version-Release number of selected component (if applicable):
vdo-6.1.0.149-16.x86_64
How reproducible:
100%
Steps to Reproduce:
1.# vdo create --device=/dev/mapper/mpathb --name=vdo_test --vdoSlabSize 0
Actual results:
Creating VDO vdo_test
Starting VDO vdo_test
Starting compression on VDO vdo_test
VDO instance 134 volume is ready at /dev/mapper/vdo_test
Expected results:
ValueError: --vdoSlabSize must be a power of two between 128M and 32G
Additional info:
At the very least, we should be consistent. If other options allow '0' to imply the 'default', then this should as well. It should also be documented, if it is not.
My general preference is that we shouldn't allow '0' to imply 'default', but I think that merits a larger discussion.
(In reply to Andy Walsh from comment #2)
> At the very least, we should be consistent. If other options allow '0' to
> imply the 'default', then this should as well. It should also be
> documented, if it is not.
>
> My general preference is that we shouldn't allow '0' to imply 'default', but
> I think that merits a larger discussion.
I agree with Andy, to the user, 0 != default
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, 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-2018:3094
Description of problem: vdo create --vdoSlabSize=0 seems to use defautl slab size (2G), but there is no mention about it in manpage or help. manpage: --vdoSlabSize=megabytes Specifies the size of the increment by which a VDO is grown. Using a smaller size constrains the total maximum physical size that can be accommodated. Must be a power of two between 128M and 32G. Using a value with a S (sectors), B (bytes), K (kilo‐bytes), M (megabytes), G (gigabytes), T (terabytes), P (petabytes) or E (exabytes) suffix is optional. If no suffix is used, the value will be interpreted as megabytes. The default is 2G. --help: --vdoSlabSize <megabytes> Specifies the size of the increment by which a VDO is grown. Using a smaller size constrains the total maximum physical size that can be accommodated. Must be a power of two between 128M and 32G; the default is 2G. Using a value with a S(ectors), B(ytes), K(ilobytes), M(egabytes), G(igabytes), T(erabytes), P(etabytes) or E(xabytes) suffix is optional. If no suffix is used, the value will be interpreted as megabytes. Note: Some values allow using '0' as default, but I cannot see the merit in it. imho it just gives some confusion and makes the manpage unnecessary longer. Version-Release number of selected component (if applicable): vdo-6.1.0.149-16.x86_64 How reproducible: 100% Steps to Reproduce: 1.# vdo create --device=/dev/mapper/mpathb --name=vdo_test --vdoSlabSize 0 Actual results: Creating VDO vdo_test Starting VDO vdo_test Starting compression on VDO vdo_test VDO instance 134 volume is ready at /dev/mapper/vdo_test Expected results: ValueError: --vdoSlabSize must be a power of two between 128M and 32G Additional info: