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 1496255 - [RFE] Incorrect reference to base10 unit in Size[UNIT] variable description
Summary: [RFE] Incorrect reference to base10 unit in Size[UNIT] variable description
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.4
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: ---
Assignee: Zdenek Kabelac
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-26 19:42 UTC by John Pittman
Modified: 2021-09-03 12:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:42:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description John Pittman 2017-09-26 19:42:11 UTC 
Description of problem:

There is an incorrect reference to base10 units in the Size[UNIT] variable description.  The description is shown below:

Size[UNIT]
  Size  is  an  input  number that accepts an optional unit.  Input units are always treated as base two values, 
  regardless of capitalization, e.g. 'k' and 'K' both refer to 1024.  The default input unit is specified by letter, 
  followed by |UNIT.  UNIT represents other possible input units: bBsSkKmMgGtTpPeE.  b|B is bytes, s|S  is  sectors  
  of 512 bytes, k|K is kilobytes, m|M is megabytes, g|G is gigabytes, t|T is terabytes, p|P is petabytes, e|E is exabytes.  
  (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)

In this description it says that input units are always treated as base two values, then goes on to say that case does not matter.  However, when showing example units, the base10 is used, as in "k|K is kilobytes".  If we're only using base2 values, then it should be "k|K is kibibytes".

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

lvm2-2.02.171-8.el7.x86_64
lvm2-libs-2.02.171-8.el7.x86_64

Expected results:

Possible edited description shown below:

Size[UNIT]
  Size  is  an  input  number that accepts an optional unit.  Input units are always treated as base two values, 
  regardless of capitalization, e.g. 'k' and 'K' both refer to 1024.  The default input unit is specified by letter, 
  followed by |UNIT. UNIT represents other possible input units: bBsSkKmMgGtTpPeE. b|B is bytes, s|S  is  sectors 
  of 512 bytes, k|K is kibibytes, m|M is mebibytes, g|G is gibibytes, t|T is tebibytes, p|P is pebibytes, e|E is 
  exbibytes. (This should not be confused with the output control --units, where capital letters mean multiple of 1000.)
Comment 3 Zdenek Kabelac 2020-10-20 21:28:27 UTC 
Pushed https://www.redhat.com/archives/lvm-devel/2020-October/msg00164.html

So we will use KiB, MiB, GiB,....  which is AFAIK more clear to most user then some 'kikibytes'

and it's matching other man pages like i.e. util-linux...
Comment 5 RHEL Program Management 2021-01-15 07:42:42 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.