Bug 2090828

Summary:	"Data alignment must not exceed device size." failure when attempting to stack PVs on small virt volumes backed by much larger storage
Product:	Red Hat Enterprise Linux 9	Reporter:	Corey Marthaler <cmarthal>
Component:	lvm2	Assignee:	Zdenek Kabelac <zkabelac>
lvm2 sub component:	Devices, Filtering and Stacking	QA Contact:	cluster-qe <cluster-qe>
Status:	CLOSED MIGRATED	Docs Contact:
Severity:	low
Priority:	medium	CC:	agk, heinzm, jbrassow, msnitzer, pasik, prajnoha, zkabelac
Version:	9.1	Keywords:	MigratedToJIRA, Triaged
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1713820	Environment:
Last Closed:	2023-09-23 18:34:55 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:	1713820
Bug Blocks:

Comment 1 Corey Marthaler 2022-05-26 16:07:34 UTC

In RHEL8 we adjusted our tests to avoid this issue and only create thin LVs/PVs > 230M. Now our tests are once again failing in RHEL9.1 as it appears the 230M minimum has increased to 270M. I'm not really keen on chasing boundary minimums for each release so I figured I'd reopen this bug to get an official response on whether or not we can just remove this test scenario from our regression matrix.

This scenario is to create many random sized virt devices, stack PVs and filesystems on them, and fstrim with fs data verification.

kernel-5.14.0-96.el9    BUILT: Thu May 19 05:31:24 AM CDT 2022
lvm2-2.03.16-1.el9    BUILT: Wed May 18 12:08:33 PM CDT 2022
lvm2-libs-2.03.16-1.el9    BUILT: Wed May 18 12:08:33 PM CDT 2022
device-mapper-1.02.185-1.el9    BUILT: Wed May 18 12:08:33 PM CDT 2022
device-mapper-libs-1.02.185-1.el9    BUILT: Wed May 18 12:08:33 PM CDT 2022



# FAILS
[root@hayes-02 tmp]# lvcreate --yes  -V 240M -T snapper_thinp/POOL -n PV10
  Logical volume "PV10" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV10
  /dev/snapper_thinp/PV10: Data alignment must not exceed device size.
  Format-specific initialisation of physical volume /dev/snapper_thinp/PV10 failed.
  Failed to setup physical volume "/dev/snapper_thinp/PV10".

# FAILS
[root@hayes-02 tmp]# lvcreate --yes  -V 242M -T snapper_thinp/POOL -n PV11
  Rounding up size to full physical extent 244.00 MiB
  Logical volume "PV11" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV11
  /dev/snapper_thinp/PV11: Data alignment must not exceed device size.
  Format-specific initialisation of physical volume /dev/snapper_thinp/PV11 failed.
  Failed to setup physical volume "/dev/snapper_thinp/PV11".

# FAILS
[root@hayes-02 tmp]# lvcreate --yes  -V 250M -T snapper_thinp/POOL -n PV12
  Rounding up size to full physical extent 252.00 MiB
  Logical volume "PV12" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV12
  /dev/snapper_thinp/PV12: Data alignment must not exceed device size.
  Format-specific initialisation of physical volume /dev/snapper_thinp/PV12 failed.
  Failed to setup physical volume "/dev/snapper_thinp/PV12".

# FAILS
[root@hayes-02 tmp]# lvcreate --yes  -V 260M -T snapper_thinp/POOL -n PV13
  Logical volume "PV13" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV13
  /dev/snapper_thinp/PV13: Data alignment must not exceed device size.
  Format-specific initialisation of physical volume /dev/snapper_thinp/PV13 failed.
  Failed to setup physical volume "/dev/snapper_thinp/PV13".

# WORKS
[root@hayes-02 tmp]# lvcreate --yes  -V 270M -T snapper_thinp/POOL -n PV15
  Rounding up size to full physical extent 272.00 MiB
  Logical volume "PV15" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV15
  Physical volume "/dev/snapper_thinp/PV15" successfully created.

# WORKS
[root@hayes-02 tmp]# lvcreate --yes  -V 280M -T snapper_thinp/POOL -n PV14
  Logical volume "PV14" created.
[root@hayes-02 tmp]# pvcreate --config devices/scan_lvs=1 /dev/snapper_thinp/PV14
  Physical volume "/dev/snapper_thinp/PV14" successfully created.

Comment 3 RHEL Program Management 2023-09-23 18:21:00 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-23 18:34:55 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.