Bug 1707481
| Summary: | creating VDO on PV fails with "Failed to make FileLayer from '/dev/disk/by-id/*'" with --force | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Krysl <jkrysl> | |
| Component: | vdo | Assignee: | Joseph Chapman <jochapma> | |
| Status: | CLOSED ERRATA | QA Contact: | Filip Suba <fsuba> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.7 | CC: | awalsh, bgurney, corwin, pasik | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | 6.1.3.4 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1710017 (view as bug list) | Environment: | ||
| Last Closed: | 2020-03-31 20:00:30 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: | 1710017 | |||
Note: This is a follow up on BZ 1620572. Mass migration to Filip. Verified with vdo version 6.1.3.4-4.
pvcreate /dev/sdb
Physical volume "/dev/sdb" successfully created.
vdo create --name vdo --device /dev/sdb --verbose --force
mkdir -p /run/lock/vdo
touch /run/lock/vdo/_etc_vdoconf.yml.lock
chmod 644 /run/lock/vdo/_etc_vdoconf.yml.lock
touch /run/lock/vdo-config-singletons
Creating VDO vdo
grep MemAvailable /proc/meminfo
blkid -s UUID -o value /dev/sdb
modprobe kvdo
vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --force /dev/disk/by-id/scsi-35000cca26c19cf3c
vdodumpconfig /dev/disk/by-id/scsi-35000cca26c19cf3c
Starting VDO vdo
dmsetup status --target vdo vdo
grep MemAvailable /proc/meminfo
modprobe kvdo
vdodumpconfig /dev/disk/by-id/scsi-35000cca26c19cf3c
dmsetup create vdo --uuid VDO-04631982-7220-4153-b25a-168f44ab00fc --table '0 19487242776 vdo /dev/disk/by-id/scsi-35000cca26c19cf3c 4096 disabled 0 32768 16380 on auto vdo ack=1,bio=4,bioRotationInterval=64,cpu=2,hash=1,logical=1,physical=1'
dmsetup status --target vdo vdo
Starting compression on VDO vdo
dmsetup message vdo 0 compression on
vdodmeventd -r vdo
dmsetup status --target vdo vdo
dmsetup status --target vdo vdo
VDO instance 0 volume is ready at /dev/mapper/vdo
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-2020:1105 |
Description of problem: VDOManager incorrectly takes the wrong /dev/disk/by-id/ path (e.g. the PV path) instead of the original disk path when changing path to persistent. This causes issues later in the process and fail. Running the same command again passes. # pvcreate /dev/sda Physical volume "/dev/sda" successfully created. # hexdump -C /dev/sda -n 4k 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00000200 4c 41 42 45 4c 4f 4e 45 01 00 00 00 00 00 00 00 |LABELONE........| 00000210 f0 5d b8 e6 20 00 00 00 4c 56 4d 32 20 30 30 31 |.].. ...LVM2 001| 00000220 4d 49 6b 39 50 53 6a 61 76 4e 47 34 62 57 55 5a |MIk9PSjavNG4bWUZ| 00000230 6c 39 73 56 62 30 4a 73 6b 5a 5a 76 63 77 56 54 |l9sVb0JskZZvcwVT| 00000240 00 00 00 80 18 09 00 00 00 00 10 00 00 00 00 00 |................| 00000250 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000260 00 00 00 00 00 00 00 00 00 10 00 00 00 00 00 00 |................| 00000270 00 f0 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000280 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 |................| 00000290 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00001000 # vdo create --name vdo --device /dev/sda --verbose mkdir -p /run/lock/vdo touch /run/lock/vdo/_etc_vdoconf.yml.lock chmod 644 /run/lock/vdo/_etc_vdoconf.yml.lock touch /run/lock/vdo-config-singletons Creating VDO vdo grep MemAvailable /proc/meminfo pvcreate --config devices/scan_lvs=1 -qq --test /dev/sda blkid -p /dev/sda vdo: ERROR - device is a physical volume; use --force to override # vdo create --name vdo --device /dev/sda --verbose --force Creating VDO vdo grep MemAvailable /proc/meminfo modprobe kvdo vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --force /dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT vdo r vdodumpconfig /dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT Removing VDO vdo vdo: ERROR - vdodumpconfig: Failed to make FileLayer from '/dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT' with No such file or directory # hexdump -C /dev/sda -n 4k 00000000 64 6d 76 64 6f 30 30 31 05 00 00 00 04 00 00 00 |dmvdo001........| 00000010 00 00 00 00 5d 00 00 00 00 00 00 00 09 01 02 00 |....]...........| 00000020 f5 b9 5f d0 ac 87 05 00 b2 c4 7b 12 6a 7b 44 af |.._.......{.j{D.| 00000030 85 b5 cd 6e 19 3f 24 0b 00 00 00 00 01 00 00 00 |...n.?$.........| 00000040 00 00 00 00 01 00 00 00 d8 5c 0a 00 00 00 00 00 |.........\......| 00000050 00 ff ff ff 00 00 00 00 00 34 c9 4a 56 00 00 00 |.........4.JV...| 00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00001000 Version-Release number of selected component (if applicable): kernel-3.10.0-1040.el7.x86_64 vdo-6.1.2.41-4.el7.x86_64 kmod-kvdo-6.1.2.41-5.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. pvcreate /dev/sda 2. vdo create --name vdo --device /dev/sda --verbose --force Actual results: vdo: ERROR - vdodumpconfig: Failed to make FileLayer from '/dev/disk/by-id/lvm-pv-uuid-MIk9PS-javN-G4bW-UZl9-sVb0-JskZ-ZvcwVT' with No such file or directory Expected results: VDO created on 1st try Additional info: