Bug 1512127
| Summary: | Creating a VDO volume over the metadata of a previously removed VDO volume fails | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Bryan Gurney <bgurney> |
| Component: | vdo | Assignee: | Ken Raeburn <raeburn> |
| Status: | CLOSED ERRATA | QA Contact: | Jakub Krysl <jkrysl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.5 | CC: | awalsh, bjohnsto, jkrysl, limershe |
| Target Milestone: | rc | Keywords: | TestBlocker |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 6.1.0.61 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 15:48:32 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: | |||
| Bug Blocks: | 1510558 | ||
|
Description
Bryan Gurney
2017-11-10 22:37:02 UTC
I forgot to finish the statement in the "Additional Info" section: It is possible to work around this by zeroing at least the VDO superblock, if not the entire geometry block, index, and VDO superblock. Setting this to 'Test Blocker' to elevate priority. This prevents us from creating another vdo. Workaround exists by zeroing the superblock, but this is more of an hack and without this workaround the vdo cannot be created again. vdo remove should probably dd the first 4k block of the device. vdo-6.1.0.72-12:
vdo remove now runs direct dd over the index superblock:
# vdo remove --name vdo --verbose
Removing VDO vdo
Stopping VDO vdo
dmsetup status vdo
mount
udevadm settle
dmsetup remove vdo
dd if=/dev/zero of=/dev/mapper/mpatha oflag=direct bs=4096 count=1
Becuase of this there is no superblock left and the next vdo is successfully created:
# vdo create --device=/dev/mapper/mpatha --name=vdo --verbose
Creating VDO vdo
pvcreate -qq --test /dev/mapper/mpatha
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 /dev/mapper/mpatha
vdodumpconfig /dev/mapper/mpatha
Starting VDO vdo
dmsetup status vdo
modprobe kvdo
vdodumpconfig /dev/mapper/mpatha
dmsetup create vdo --uuid VDO-b3d10bf0-209b-4ea3-a24e-b70c35de5871 --table '0 209715200 dedupe /dev/mapper/mpatha 4096 disabled 0 32768 16380 on sync vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
dmsetup status vdo
Starting compression on VDO vdo
dmsetup message vdo 0 compression on
dmsetup status vdo
VDO instance 1 volume is ready at /dev/mapper/vdo
/var/log/messages:
[ 1498.607669] kvdo1:dmsetup: starting device 'vdo' device instantiation 1 (ti=ffffb2dd81031040) write policy sync
[ 1498.657060] kvdo1:dmsetup: zones: 1 logical, 1 physical, 1 hash; base threads: 5
[ 1498.805539] kvdo1:dmsetup: uds: kvdo1:dedupeQ: loading or rebuilding index: dev=/dev/mapper/mpatha offset=4096 size=2781704192
[ 1498.805903] uds: kvdo1:dedupeQ: Failed loading or rebuilding index: UDS Error: No index found (1061)
[ 1498.805910] kvdo1:dedupeQ: Error opening index dev=/dev/mapper/mpatha offset=4096 size=2781704192: UDS Error: No index found (1061)
uds: kvdo1:dedupeQ: creating index: dev=/dev/mapper/mpatha offset=4096 size=2781704192
uds: kvdo1:dedupeQ: Using 6 indexing zones for concurrency.
[ 1499.018973] Setting UDS index target state to online
[ 1499.042948] kvdo1:dmsetup: device 'vdo' started
[ 1499.064259] kvdo1:dmsetup: resuming device 'vdo'
[ 1499.085649] kvdo1:dmsetup: device 'vdo' resumed
[ 1499.124396] kvdo1:packerQ: compression is enabled
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/RHEA-2018:0871 |