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:
Create LVM volume (1TB), convert it to VDO, then extend the LVM by 5 MB and growPhysical the VDO. VDO will fail with very unfriendly error.
Version-Release number of selected component (if applicable):
vdo-6.1.0.124-14.x86_64
kmod-kvdo-6.1.0.124-11.el7.x86_64
How reproducible:
deterministic
Steps to Reproduce:
1. lvcreate -L 1T -n vdosrv vol0
2. vdo create --name=srv18 --device=/dev/vol0/vdosrv --vdoLogicalSize=2T
3. lvresize -L +5M /dev/mapper/vol0-srv
4. vdo growPhysical -n srv18 --verbose
Actual results:
[root@dell-per610-03 ~]# LC_ALL=C vdo growPhysical -n srv18
vdo: ERROR - Cannot prepare to grow physical on VDO srv18; device-mapper: message ioctl on srv18 failed: Input/output error
vdo: ERROR - device-mapper: message ioctl on srv18 failed: Input/output error
[root@dell-per610-03 ~]# LC_ALL=C vdo growPhysical -n srv18 --verbose
vdodumpconfig /dev/vol0/vdosrv
dmsetup status srv18
dmsetup resume srv18
dmsetup status srv18
dmsetup message srv18 0 prepareToGrowPhysical
vdo: ERROR - Cannot prepare to grow physical on VDO srv18; device-mapper: message ioctl on srv18 failed: Input/output error
vdo: ERROR - device-mapper: message ioctl on srv18 failed: Input/output error
Expected results:
Error: Only 5MB of additional space on block device. We can grow only if there is more than XXXX MB free space.
This may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1508926 but the error messege I am getting is different. So I filed new report.
/var/log/messages:
[23282.869934] kvdo1:dmsetup: Preparing to resize physical to 268437504
[23282.876322] kvdo: dmsetup: mapToSystemError: mapping internal status code 2065 (kvdo: VDO_INCREMENT_TOO_SMALL: kvdo: Physical block growth of too few blocks) to EIO
This seems to be a different condition from BZ 1508926, which had the dmsetup message of "Requested physical block count 5242880 not greater than 5242880"
In the man page for vdo(8), there's this sectino for the growPhysical subcommand:
growPhysical
Grows the physical size of a VDO volume. The volume must exist
and must be running. This command must be run with root privi‐
leges. Applicable options include:
--name=volume (required)
--confFile=file
--verbose
--logfile=file
...but the help text of the "--vdoSlabSize" option states that the option "Specifies the size of the increment by which a VDO is grown." This is true; in order to execute a growPhysical operation on a VDO volume, there needs to be enough unused space to store at least one slab (default 2 GB, but this could be as small as 128 MB, or as large as 32 GB, depending on the initial configuration of the VDO volume).
I think the fix for this should include both manpage change (adding the information of using at least 1 * vdoSlabSize to growPhysical) and 'vdo growPhysical' command checking that the physical size is at least 1* vdoSlabSize.
Just checking the size of the increment at a higher level can result in an unnecessary when there is extra space on the volume because it wasn't already an exact multiple of the slab size (there's extra space, less than a full slab, already unused on the volume).
I think this is actually the same issue as BZ 1512134, which is another case of not having enough space to do the grow physical.
*** This bug has been marked as a duplicate of bug 1512134 ***
Description of problem: Create LVM volume (1TB), convert it to VDO, then extend the LVM by 5 MB and growPhysical the VDO. VDO will fail with very unfriendly error. Version-Release number of selected component (if applicable): vdo-6.1.0.124-14.x86_64 kmod-kvdo-6.1.0.124-11.el7.x86_64 How reproducible: deterministic Steps to Reproduce: 1. lvcreate -L 1T -n vdosrv vol0 2. vdo create --name=srv18 --device=/dev/vol0/vdosrv --vdoLogicalSize=2T 3. lvresize -L +5M /dev/mapper/vol0-srv 4. vdo growPhysical -n srv18 --verbose Actual results: [root@dell-per610-03 ~]# LC_ALL=C vdo growPhysical -n srv18 vdo: ERROR - Cannot prepare to grow physical on VDO srv18; device-mapper: message ioctl on srv18 failed: Input/output error vdo: ERROR - device-mapper: message ioctl on srv18 failed: Input/output error [root@dell-per610-03 ~]# LC_ALL=C vdo growPhysical -n srv18 --verbose vdodumpconfig /dev/vol0/vdosrv dmsetup status srv18 dmsetup resume srv18 dmsetup status srv18 dmsetup message srv18 0 prepareToGrowPhysical vdo: ERROR - Cannot prepare to grow physical on VDO srv18; device-mapper: message ioctl on srv18 failed: Input/output error vdo: ERROR - device-mapper: message ioctl on srv18 failed: Input/output error Expected results: Error: Only 5MB of additional space on block device. We can grow only if there is more than XXXX MB free space. This may be related to https://bugzilla.redhat.com/show_bug.cgi?id=1508926 but the error messege I am getting is different. So I filed new report.