2090828 – "Data alignment must not exceed device size." failure when attempting to stack PVs on small virt volumes backed by much larger storage

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

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 2090828 - "Data alignment must not exceed device size." failure when attempting to stack PVs on small virt volumes backed by much larger storage

Summary: "Data alignment must not exceed device size." failure when attempting to stac...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	lvm2
Sub Component:
Version:	9.1
Hardware:	x86_64
OS:	Linux
Priority:	medium
Severity:	low
Target Milestone:	rc
Target Release:	---
Assignee:	Zdenek Kabelac
QA Contact:	cluster-qe
Docs Contact:
URL:
Whiteboard:
Depends On:	1713820
Blocks:
TreeView+	depends on / blocked

Reported:	2022-05-26 16:00 UTC by Corey Marthaler
Modified:	2023-09-23 18:34 UTC (History)
CC List:	7 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	1713820
Environment:
Last Closed:	2023-09-23 18:34:55 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-8287	0	None	Migrated	None	2023-09-23 18:34:49 UTC
Red Hat Issue Tracker	RHELPLAN-123493	0	None	None	None	2022-05-26 16:18:29 UTC

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.

Note You need to log in before you can comment on or make changes to this bug.