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.
Description of problem:
When detecting the disk layout for a system with Advanced Format (AF) disks, the size of the disk is incorrect.
Version-Release number of selected component (if applicable):
rear-1.17.2-6.el7
How reproducible:
Easily, with the correct disks
Steps to Reproduce:
1. Install and configure rear for basic use including most/all local storage
2. Verify that one or more disks report a value greater than 512 for /sys/block/<disk>/queue/logical_block_size
3. Create a rescue image
4. Verify in the resulting disklayout.conf that the size of the disk is correct
Actual results:
The disk will be reported as significantly larger than it actually is
Expected results:
The disk will be reported as the correct size
Additional info:
This is due to the use of the "logical_block_size" interface exposed by the kernel via the sysfs filesystem. The value found is used as the multiplier for the "size" interface. However, the "size" interface is always in 512 byte blocks. Regardless of the "logical_block_size".