Bug 1710017

Summary: creating VDO on PV fails with "Failed to make FileLayer from '/dev/disk/by-id/*'" with --force
Product: Red Hat Enterprise Linux 8 Reporter: Andy Walsh <awalsh>
Component: vdoAssignee: Joseph Chapman <jochapma>
Status: CLOSED ERRATA QA Contact: vdo-qe
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: awalsh, bgurney, jkrysl, sweettea
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 6.2.1.133 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1707481 Environment:
Last Closed: 2019-11-05 22:12:41 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: 1707481    
Bug Blocks:    

Comment 2 Jakub Krysl 2019-08-21 11:16:02 UTC
kmod-kvdo-6.2.1.134-56.el8.x86_64
vdo-6.2.1.134-11.el8.x86_64

# 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  da c6 14 bc 20 00 00 00  4c 56 4d 32 20 30 30 31  |.... ...LVM2 001|
00000220  30 68 30 59 34 6d 4f 38  42 61 41 42 55 42 34 76  |0h0Y4mO8BaABUB4v|
00000230  38 36 74 32 71 44 64 36  45 76 49 73 4d 53 46 73  |86t2qDd6EvIsMSFs|
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
Creating VDO vdo
    grep MemAvailable /proc/meminfo
    pvcreate --config devices/scan_lvs=1 -qq --test /dev/sda
    blkid -p --no-part-details /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
    blkid -s UUID -o value /dev/sda
    modprobe kvdo
    vdoformat --uds-checkpoint-frequency=0 --uds-memory-size=0.25 --force /dev/disk/by-id/scsi-35000cca26c1a0a38
    vdodumpconfig /dev/disk/by-id/scsi-35000cca26c1a0a38
Starting VDO vdo
    dmsetup status --target vdo vdo
    grep MemAvailable /proc/meminfo
    modprobe kvdo
    vdodumpconfig /dev/disk/by-id/scsi-35000cca26c1a0a38
    vdodumpconfig /dev/disk/by-id/scsi-35000cca26c1a0a38
    dmsetup create vdo --uuid VDO-69fb9695-a517-43f0-a178-ee90058e0f37 --table '0 19487242776 vdo V2 /dev/disk/by-id/scsi-35000cca26c1a0a38 2441609216 4096 32768 16380 on auto vdo maxDiscard 1 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
VDO instance 1 volume is ready at /dev/mapper/vdo

# 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 94 09 02 00  |....]...........|
00000020  b9 19 e1 a1 9e 90 05 00  69 fb 96 95 a5 17 43 f0  |........i.....C.|
00000030  a1 78 ee 90 05 8e 0f 37  00 00 00 00 01 00 00 00  |.x.....7........|
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 33 81 82 ff 00 00 00  |.........3......|
00000060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00001000


VDO nnow does not touch the disk without --force. But if it is given, it correctly replaces the PV and creates the device.

Comment 5 errata-xmlrpc 2019-11-05 22:12:41 UTC
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-2019:3548