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:
busybox 'du' applet reports different sizes with -h and -m parameters comparing to coreutils 'du' on small files

Version-Release number of selected component (if applicable):
busybox-1.15.1-15.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. `dd if=/dev/zero of=/tmp/testfile.tmp bs=1128k count=1`
2. check `du -h /tmp/testfile.tmp` and analogically with busybox
3. compare results
  
Actual results:
 comparation of last line with -h parameter
	busybox			|	coreutils
>1.1M	/tmp/testfile.tmp	| 1.2M	/tmp/testfile.tmp

 comparation of last line with -m parameter
	busybox			|	coreutils
>1	/tmp/testfile.tmp	| 2	/tmp/testfile.tmp

Expected results:
busybox 'du' reports same sizes when approximating as coreutils 'du' does

Coreutils rounds sizes up, busybox rounds to nearest.

Not sure whether this needs to be fixed...

For now I added a comment in the upstream busybox source explaining this.

Closing as WONTFIX. This doesn't look important.