Bug 1755448
Summary: | Do not start index when creating device with deduplication=disabled | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Jakub Krysl <jkrysl> |
Component: | vdo | Assignee: | Matthew Sakai <msakai> |
Status: | CLOSED ERRATA | QA Contact: | Filip Suba <fsuba> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.2 | CC: | awalsh, bgurney, corwin, fsuba, msakai |
Target Milestone: | rc | ||
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 6.2.3.77 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 02:01:16 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
2019-09-25 14:16:13 UTC
Mass migration to Filip. Verified with vdo-6.2.3.114-14.el8. # vdo create --name vdo1 --device /dev/sda --indexMem 10 --deduplication disabled; for i in `seq 1 50`; do free -m | grep Mem:; sleep 0.1; done; vdo remove --all Creating VDO vdo1 Logical blocks defaulted to 2408694391 blocks. The VDO volume can address 8 TB in 4603 data slabs, each 2 GB. It can grow to address at most 16 TB of physical storage in 8192 slabs. If a larger maximum size might be needed, use bigger slabs. Starting VDO vdo1 Starting compression on VDO vdo1 VDO instance 1 volume is ready at /dev/mapper/vdo1 Mem: 64020 3487 59960 17 571 59852 Mem: 64020 3487 59960 17 571 59852 Mem: 64020 3487 59960 17 571 59852 Mem: 64020 3488 59960 17 571 59852 Mem: 64020 3487 59961 17 571 59853 Mem: 64020 3487 59961 17 572 59853 Mem: 64020 3487 59961 17 572 59853 Mem: 64020 3487 59961 17 572 59853 ... Mem: 64020 3489 59958 17 572 59850 Mem: 64020 3489 59958 17 572 59850 Mem: 64020 3489 59958 17 572 59850 Mem: 64020 3489 59958 17 572 59850 Removing VDO vdo1 Stopping VDO vdo1 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 (kmod-kvdo bug fix and enhancement update), 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-2020:4551 |