RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2037530 - vdo import doesn't detect previous value of logicalBlockSize
Summary: vdo import doesn't detect previous value of logicalBlockSize
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: vdo
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: bjohnsto
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-05 20:15 UTC by Strahil Nikolov
Modified: 2022-05-10 16:34 UTC (History)
5 users (show)

Fixed In Version: vdo-6.2.6.14-14.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-10 15:21:06 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-106923 0 None None None 2022-01-05 20:19:57 UTC
Red Hat Product Errata RHBA-2022:2028 0 None None None 2022-05-10 15:21:12 UTC

Description Strahil Nikolov 2022-01-05 20:15:31 UTC 
Description of problem:
When importing VDO device from CentOS 7.9 to CentOS Stream , vdo import doesn't detect previous size of "logicalBlockSize" 

Version-Release number of selected component (if applicable):
vdo-6.2.6.7-14.el8.x86_64
libblockdev-vdo-2.24-8.el8.x86_64
kmod-kvdo-6.2.5.72-81.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Reinstall OS to CentOS Stream 9
2.Import the vdo device:
vdo import --name somename --device /dev/nvme0n1

3.Start GlusterFS
4.Install RHV HostedEngine (or oVirt HE)
hosted-engine --deploy --restore-from-file=engine_backup

5. Start the storage domain that is a brick for Gluster

Actual results:
grep logicalBlockSize /etc/vdoconf.yml 
      logicalBlockSize: 4096

Expected results:
# VDO import should detect correct logicalBlockSize
grep logicalBlockSize /etc/vdoconf.yml 
      logicalBlockSize: 512

Additional info:
A workaround to restore oVirt/RHV Gluster-based Storage domain is to:

# Set the domain in maintenance
# Umount the brick
umount /gluster_bricks/fast
# Disable VG
vgchange gluster_vg_nvme
# Stop and disable the VDO device
vdo stop -n somename
vdo deactivate -n somename
# Remove existing config:
rm -f /etc/vdoconf.yml
# Reimport the VDO device with necessary logical block size:
vdo import --emulate512=enabled -n vdo_gluster_fast --device /dev/nvme0n1
Comment 1 bjohnsto 2022-01-11 23:32:11 UTC 
Unfortunately, there are several configuration parameters that are not stored in the VDO volume itself; only in the VDO config file. So when you lose that file via reinstall or moving the device somewhere else, the command "vdo import" is not able to find the old values, and resorts to using defaults. In this case, the default value for logicalBlockSize is 4096. The good news (sort of .. as you have shown) is that these configuration parameters are allowed on the "vdo import" command line, so if you can remember them, you can simply type them back in. 

Full removal of the config file after "incorrect" import is also likely not the best thing to be doing since there might be other entries in the config file. Unfortunately we have no current way to remove an entry from the config file only and not actually affect the VDO volume it relates to. Maybe a "vdo clear" command would be something we should add to help in scenarios like this.
Comment 2 Strahil Nikolov 2022-01-11 23:48:31 UTC 
Thanks for the clarification.
Maybe in future versions, VDO can keep the block size in the metadata.

To be honest, I couldn't find anything related to 'VDO import' in the RHEL 8 docs.
Updating RHEL docs,that the  logicalBlockSize is not in the metadata and on import it must be specified by the Admin, is a good start.
Comment 3 bjohnsto 2022-01-17 20:36:13 UTC 
Agreed. I'll be updating the docs.
Comment 7 Filip Suba 2022-02-28 12:29:52 UTC 
Verified with vdo-6.2.6.14-14.el8.
Comment 9 errata-xmlrpc 2022-05-10 15:21:06 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 (vdo 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-2022:2028
Note You need to log in before you can comment on or make changes to this bug.