Bug 1543921
| Summary: | vdo start --forceRebuild gives wrong error | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Krysl <jkrysl> |
| Component: | vdo | Assignee: | Bryan Gurney <bgurney> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.5 | CC: | awalsh, bgurney, jkrysl, limershe |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.1.18 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-30 09:39:22 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: | |||
|
Description
Jakub Krysl
2018-02-09 15:18:59 UTC
When I try this on my system with 6.1.0.146 installed, I see this message in /var/log/messages: UDS/vdoforcerebuild[20440]: ERROR (vdoforcerebuild/20440) Can't force rebuild on a normal VDO: VDO Status: The device is not in a clean state (2064) This is correct; the "vdo start --forceRebuild" command will only run on a VDO volume that has an operating mode of "read-only". This message is slightly different that what appears in stdout on the shell that executed the "vdo start --forceRebuild" command. (In reply to Bryan Gurney from comment #2) > When I try this on my system with 6.1.0.146 installed, I see this message in > /var/log/messages: > > UDS/vdoforcerebuild[20440]: ERROR (vdoforcerebuild/20440) Can't force > rebuild on a normal VDO: VDO Status: The device is not in a clean state > (2064) > > This is correct; the "vdo start --forceRebuild" command will only run on a > VDO volume that has an operating mode of "read-only". This message is > slightly different that what appears in stdout on the shell that executed > the "vdo start --forceRebuild" command. Except it's not. The error says the device is not in a clean state, when it really is. Is there a difference between "clean" and "read-only"? The message "The device is not in a clean state" makes me think "I need to rebuild", but then the forced rebuild doesn't run for that message. It seems be incorrectly worded to the outsider. Tested on:
RHEL-7.6-20180626.0
kernel-3.10.0-915.el7
kmod-vdo-6.1.1.99-1.el7
vdo-6.1.1.99-2.el7
# vdo create --name vdo --device /dev/sdb
Creating VDO vdo
Starting VDO vdo
Starting compression on VDO vdo
VDO instance 0 volume is ready at /dev/mapper/vdo
# vdo stop --name vdo
Stopping VDO vdo
# vdo start --name vdo --forceRebuild --verbose
Starting VDO vdo
dmsetup status vdo
grep MemAvailable /proc/meminfo
modprobe kvdo
vdoforcerebuild /dev/disk/by-id/scsi-360fff19abdd9b56dfb9bf59625f4c9f7
vdo: ERROR - Device vdo not read-only
vdo: ERROR - Could not set up device mapper for vdo
vdo: ERROR - vdoforcerebuild: forceRebuild failed on '/dev/disk/by-id/scsi-360fff19abdd9b56dfb9bf59625f4c9f7': VDO Status: The device is not in read-only mode
The message no longer suggest the device is dirty.
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 |