Bug 1597886
| Summary: | vdo growPhysical command on non-expanded device no longer prints message regarding lack of additional space | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Bryan Gurney <bgurney> |
| Component: | kmod-kvdo | Assignee: | Matthew Sakai <msakai> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.6 | CC: | awalsh, jkrysl, msakai, rhandlin |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.1.108 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-30 09:39:49 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: | |||
| Bug Depends On: | 1576539 | ||
| Bug Blocks: | |||
|
Description
Bryan Gurney
2018-07-03 19:55:41 UTC
Description of problem: If the user tries to run "vdo growPhysical" on a VDO volume without having increased the size of the backing device, they will receive a message stating "message ioctl on <volume> failed: Invalid argument", without a helpful kernel log message regarding the reason why the growPhysical attempt failed (i.e.: the requested physical block count did not increase). I think the reduced number of messages in /var/log/messages is caused by fix in BZ 1576539. The rest being asked in this BZ is already being asked in BZ 1512134 (exposing the messages), except here we have 0 growth and in BZ 1512134 it is growth too small. Matthew is it the fix the same for this BZ and BZ 1512134 (so we should close this a dup) or is it different? Jakub, I think you are correct that is a side-effect of the way we fixed BZ 1576539. BZ 1512134 is about exposing the error message through the user management script instead of only through log messages. This BZ is about having sufficient information in the log messages. So, I believe they are different and I will fix this one shortly. kmod-kvdo-6.1.1.111-1.el7:
# vdo growPhysical --name=vdo --verbose
vdodumpconfig /dev/disk/by-id/scsi-3600140550ade793f6124ab5b420f3c20-part1
dmsetup status vdo
dmsetup resume vdo
vdodmeventd -r vdo
dmsetup status vdo
dmsetup message vdo 0 prepareToGrowPhysical
vdo: ERROR - Cannot prepare to grow physical on VDO vdo; device-mapper: message ioctl on vdo failed: Invalid argument
vdo: ERROR - device-mapper: message ioctl on vdo failed: Invalid argument
/var/log/messages:
[165807.507587] kvdo85:dmsetup: Preparing to resize physical to 19660544
[165807.539492] kvdo85:dmsetup: Requested physical block count 19660544 not greater than 19660544
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 |