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 1511871 - vdoformat has no limit for physical size if physical size is over 256T
Summary: vdoformat has no limit for physical size if physical size is over 256T
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: John Wiele
QA Contact: Filip Suba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-10 10:35 UTC by Jakub Krysl
Modified: 2020-03-31 20:00 UTC (History)
8 users (show)

Fixed In Version: 6.1.0.149
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:00:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1105 0 None None None 2020-03-31 20:00:39 UTC

Description Jakub Krysl 2017-11-10 10:35:12 UTC 
Description of problem:
I tried creating VDO on top of VDO with maximum allowed logical size 4P. because of this the upper VDO thinks physical size is actually 4P and fails with error:
vdo: ERROR - vdoformat: vdo.c:507: handleAssertionFailure: Assertion `config->physicalBlocks <= MAXIMUM_PHYSICAL_BLOCKS' failed.

Version-Release number of selected component (if applicable):
vdo-6.1.0.34-8

How reproducible:
100%

Steps to Reproduce:
1. vdo create --device DEVICE --name VDO --vdoLogicalSize 4P
2. vdo create --device /dev/mapper/VDO --name VDO2

Actual results:
vdo: ERROR - vdoformat: vdo.c:507: handleAssertionFailure: Assertion `config->physicalBlocks <= MAXIMUM_PHYSICAL_BLOCKS' failed.

Expected results:
Actually not sure, maybe create VDO on only part of the block device and leaving the rest free. Or output error that the underlaying block device is too large, max size 256T.

Additional info:
Comment 2 Dennis Keefe 2017-11-10 13:38:52 UTC 
Physical volumes larger than 256TB are not supported.  User should resize the volume to a smaller size otherwise the user might believe that there is additional available blocks to use or grow into.
Comment 3 Louis Imershein 2017-11-10 18:03:59 UTC 
What's the practical use case for the behavior being suggested?
Comment 4 Jakub Krysl 2017-11-14 10:38:35 UTC 
I cannot think of practical usage of VDO over VDO, but the bug this is hitting is not limited to just VDO over VDO. Wherever user tries to create VDO over storage larger than 256TB, this error should appear. (correct me if I am wrong)

So the most practical usage case I can think of would be creating VDO over array larger than 256TB. As VDO does not support sizes larger than 256TB, I suggest fixing this by giving the user exactly this information right away instead of uncaught error. This way user can split the storage however he likes.
Comment 5 bjohnsto 2017-11-14 18:40:56 UTC 
This seems like something vdoFormat could check and provide a better error message for.
Comment 11 Jakub Krysl 2019-10-15 14:38:54 UTC 
Mass migration to Filip.
Comment 12 Filip Suba 2020-01-07 12:56:43 UTC 
Verified with vdo version 6.1.3.4-4.

vdo: ERROR - vdoformat: underlying block device size exceeds the maximum (281474976710656)
Comment 14 errata-xmlrpc 2020-03-31 20:00:30 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, 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:1105
Note You need to log in before you can comment on or make changes to this bug.