-
Bug
-
Resolution: Done-Errata
-
Major
-
rhel-8.9.0
-
None
-
lvm2-2.03.14-13.el8_9
-
None
-
Moderate
-
rhel-sst-logical-storage
-
ssg_filesystems_storage_and_HA
-
22
-
24
-
1
-
QE ack, Dev ack
-
False
-
-
None
-
None
-
-
x86_64
-
None
What were you trying to do that didn't work?
[root@virt-242 ~]# vdo create --force --name lvm_import_vdo_sanity
--vdoLogicalSize 3.00k --device /dev/sda1
Creating VDO lvm_import_vdo_sanity
Found existing signature on
/dev/disk/by-id/scsi-1LIO-ORGcluster152688-d:0618652b-2df0-4693-9c9f-995b89c3e57e-part1
at offset 0: LABEL="(null)"
UUID="adbdad12-3c36-43d0-8942-7c2f67c797b0" TYPE="vdo" USA
GE="other".
Formatting device already containing a known signature.
Logical blocks defaulted to 18838215 blocks.
The VDO volume can address 72 GB in 36 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 lvm_import_vdo_sanity
Starting compression on VDO lvm_import_vdo_sanity
VDO instance 65 volume is ready at /dev/mapper/lvm_import_vdo_sanity
[root@virt-242 ~]# lvm_import_vdo --yes
/dev/disk/by-id/scsi-1LIO-ORGcluster152688-d:0618652b-2df0-4693-9c9f-995b89c3e57e-part1
Stopping VDO lvm_import_vdo_sanity
Converting VDO lvm_import_vdo_sanity
Checking device
Non converted VDO. Converting to LVM
Opening /dev/mapper/VDO_lvm_import_vdo_2327530790_snap exclusively
Loading the VDO superblock and volume geometry
Checking the VDO state
New geometry block offset calculated at 2056192
Converting the UDS index
Converting the VDO
Conversion completed for
'/dev/mapper/VDO_lvm_import_vdo_2327530790_snap': VDO is now aligned
on 2097152 bytes, starting at offset 2056192
Physical volume "/dev/mapper/VDO_lvm_import_vdo_2327530790_snap"
successfully created.
Volume group "vdovg" successfully created
WARNING: Logical volume vdovg/vdolvol_vpool not zeroed.
Logical volume "vdolvol_vpool" created.
WARNING: Converting logical volume vdovg/vdolvol_vpool to VDO pool
volume WITHOUT formating.
WARNING: Using invalid VDO pool data MAY DESTROY YOUR DATA!
Logical volume "vdolvol" created.
Converted vdovg/vdolvol_vpool to VDO pool volume and created virtual
vdovg/vdolvol VDO volume.
lvextend: unrecognized option '--fs'
Error during parsing of command line.
if [ "$vdo_logicalSizeRounded" -lt "$vdo_logicalSize" ]; then
# need to extend virtual size to be covering all the
converted area
# let lvm2 to round to the proper virtual size of VDO LV
dry "$LVM" lvextend $YES $VERB --fs ignore --devices
"$device" -L "$vdo_logicalSize"k "$VGNAME/$LVNAME"
fi
Please provide the package NVR for which bug is seen:
kernel-4.18.0-513.el8 BUILT: Fri Aug 25 19:22:49 CEST 2023
lvm2-2.03.14-11.el8_9 BUILT: Thu Sep 7 21:47:30 CEST 2023
lvm2-libs-2.03.14-11.el8_9 BUILT: Thu Sep 7 21:47:30 CEST 2023
- links to
-
RHBA-2024:128184 lvm2 bug fix and enhancement update