Bug 1600662
| Summary: | Growing physical size should not suspend vdo device when the size is equal [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Reznik <jreznik> |
| Component: | kmod-kvdo | Assignee: | Matthew Sakai <msakai> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.5 | CC: | awalsh, bgurney, jkrysl, jreznik, msakai, rhandlin |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | Flags: | msakai:
needinfo-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.181 | Doc Type: | If docs needed, set a value |
| Doc Text: |
Previously, VDO volumes were unable to grow if the underlying block device increased in size while the system was powered off or the VDO volume was offline. With this update, VDO correctly checks the requested size and the current size of the device, and, as a result, the described problem no longer occurs.
|
Story Points: | --- |
| Clone Of: | 1576539 | Environment: | |
| Last Closed: | 2018-08-16 14:19:04 UTC | Type: | --- |
| 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
Jaroslav Reznik
2018-07-12 17:44:27 UTC
kmod-kvdo-6.1.0.181-17.el7_5
kernel-3.10.0-862.10.2.el7
# vdo growPhysical --name vdo --verbose
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:
[ 672.869364] kvdo1:dmsetup: Preparing to resize physical to 10485759
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:2450 |