Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1830904

Summary: allow_mixed_block_sizes option missing again in lvm.conf
Product: Red Hat Enterprise Linux 7 Reporter: Juraj Hrdlica <jhrdlica>
Component: lvm2Assignee: Marian Csontos <mcsontos>
lvm2 sub component: Configuration files QA Contact: cluster-qe <cluster-qe>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: agk, cmarthal, heinzm, jbrassow, lvm-team, mcsontos, msnitzer, prajnoha, pvlasin, rbednar, teigland, zkabelac
Version: 7.9Keywords: Regression
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: lvm2-2.02.187-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-29 19:55:48 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 Juraj Hrdlica 2020-05-04 09:42:37 UTC 
This is basically a regression of BZ1669751. The option to allow mixed block sizes was left out and added later, now it's missing again in RHEL7.9
 
 
RHEL 7.8
 
# grep allow_mixed_block_sizes /etc/lvm/lvm.conf
        # Configuration option devices/allow_mixed_block_sizes.
        allow_mixed_block_sizes = 1
 
# rpm -q lvm2
lvm2-2.02.186-7.el7_8.1.x86_64
 
==============================
RHEL 7.9
 
# grep allow_mixed_block_sizes /etc/lvm/lvm.conf
# echo $?
1
# rpm -q lvm2
lvm2-2.02.187-2.el7.x86_64
Comment 5 David Teigland 2020-05-04 15:03:38 UTC 
This setting has been tweaked by a number of commits, and I don't know if that version has all of them:

96fd312e85ce config: allow_mixed_block_sizes set version 2.02.187
f53cce180423 config: allow_mixed_block_sizes set default to 1
c2853147639c Revert "Revert "vgcreate/vgextend: restrict PVs with mixed block sizes""
c37aa7881d84 Revert "vgcreate/vgextend: restrict PVs with mixed block sizes"
a57b92dec396 vgcreate/vgextend: restrict PVs with mixed block sizes


The latest head of the stable branch works correctly:

[root@null-02 lvm.git]# lvmconfig --type default | grep allow_mixed
        allow_mixed_block_sizes=1

[root@null-02 lvm.git]# lvmconfig --version
  LVM version:     2.02.188(2)-git (2020-03-24)
  Library version: 1.02.172-git (2020-03-24)
  Driver version:  4.37.1
  Configuration:   ./configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-default-dm-run-dir=/run --with-default-run-dir=/run/lvm --with-default-pid-dir=/run --with-default-locking-dir=/run/lock/lvm --with-usrlibdir=/usr/lib64 --enable-fsadm --with-pool=internal --enable-write_install --with-user= --with-group= --with-device-uid=0 --with-device-gid=6 --with-device-mode=0660 --enable-pkgconfig --enable-applib --enable-cmdlib --with-cluster=internal --with-clvmd=corosync --with-udevdir=/usr/lib/udev/rules.d --enable-udev_sync --with-thin=internal --with-thin-check=/usr/sbin/thin_check --with-thin-dump=/usr/sbin/thin_dump --with-thin-repair=/usr/sbin/thin_repair --enable-lvmetad --enable-udev-systemd-background-jobs --with-cache=internal --enable-lvmpolld --with-clvmd=singlenode --enable-lvmlockd-sanlock --enable-lvmlockd-dlm --enable-debug --enable-dmeventd --enable-python3_bindings
Comment 11 Corey Marthaler 2020-05-22 18:30:52 UTC 
Fix verified in the latest rpms.

lvm2-2.02.187-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
lvm2-libs-2.02.187-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
lvm2-cluster-2.02.187-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
lvm2-lockd-2.02.187-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
device-mapper-1.02.170-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
device-mapper-libs-1.02.170-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
device-mapper-event-1.02.170-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020
device-mapper-event-libs-1.02.170-3.el7    BUILT: Tue May 19 06:05:10 CDT 2020


[root@hayes-01 ~]# grep allow_mixed_block_sizes /etc/lvm/lvm.conf
        # Configuration option devices/allow_mixed_block_sizes.
        allow_mixed_block_sizes = 1
Comment 13 errata-xmlrpc 2020-09-29 19:55:48 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 (lvm2 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:3927