Bug 1075679
| Summary: | Cannot rebuild coreutils on XFS filesystem - sparse test fails | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Pat Riehecky <riehecky> |
| Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> |
| Status: | CLOSED ERRATA | QA Contact: | Tomas Dolezal <todoleza> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.5 | CC: | csieh, misterbonnie, psklenar |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 06:34:32 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Pat Riehecky
2014-03-12 15:09:01 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 ). 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 |