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 1075679 - Cannot rebuild coreutils on XFS filesystem - sparse test fails
Summary: Cannot rebuild coreutils on XFS filesystem - sparse test fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: coreutils
Version: 6.5
Hardware: x86_64
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Ondrej Vasik
QA Contact: Tomas Dolezal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-12 15:09 UTC by Pat Riehecky
Modified: 2014-10-14 06:34 UTC (History)
3 users (show)

Fixed In Version: coreutils-8.4-33.el6
Doc Type: Bug Fix
Doc Text:
Cause: Some filesystems (like XFS) may have special features like speculative preallocation of holes. Consequence: This can cause failure of the dd test in the upstream testsuite - and therefore failure of the rebuild on xfs filesystem. Fix: Test logic was improved to prevent failures in such situations. Result: Coreutils package source rpm can be rebuilt even on xfs.
Clone Of:
Environment:
Last Closed: 2014-10-14 06:34:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1457 0 normal SHIPPED_LIVE coreutils bug fix and enhancement update 2014-10-14 01:10:58 UTC

Description Pat Riehecky 2014-03-12 15:09:01 UTC 
Description of problem: The dd/sparse test fails when run on the XFS filesystem.  The exact same binaries run on EXT4 pass the test.

The failing test is on line 62 of tests/dd/sparse


Version-Release number of selected component (if applicable):coreutils-8.4-31.el6_5.1


How reproducible:100%


Steps to Reproduce:
1.populate buildroot on XFS
2.rpmbuild -bb coreutils*.src.rpm
3.build fails
4.repeat on EXT4, build passes

Actual results:
dd sparse test does not work on XFS

Expected results:
dd sparse test should work on all supported filesystems

Additional info:
Comment 2 Ondrej Vasik 2014-03-12 15:27:39 UTC 
Upstream fixes that issue by http://git.savannah.gnu.org/cgit/coreutils.git/commit/tests/dd/sparse?id=8195165839877eece7984dd08613323e96424cea and http://git.savannah.gnu.org/cgit/coreutils.git/commit/tests/dd/sparse?id=d42f3a4d41034d099bf29ade22221b401528c060 ... actually more filesystems seem to be an issue for that specific tests (e.g. NFS - where some parts need to be skipped - http://git.savannah.gnu.org/cgit/coreutils.git/commit/tests/dd/sparse?id=4b101ccd176eb3951bfbab717a0a3b5e2c4d19ef ).
Comment 7 errata-xmlrpc 2014-10-14 06:34:32 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.

http://rhn.redhat.com/errata/RHBA-2014-1457.html
Note You need to log in before you can comment on or make changes to this bug.