Bug 619139
Summary: | fsck returns zero instead of error code | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Bryn M. Reeves <bmr> | ||||
Component: | util-linux-ng | Assignee: | Karel Zak <kzak> | ||||
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 6.0 | CC: | azelinka, jmarko, ltroan, rvokal, sct, tao, tumeya | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | util-linux-ng-2.17.2-9.el6 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | 618134 | Environment: | |||||
Last Closed: | 2011-05-19 14:05:51 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Bryn M. Reeves
2010-07-28 16:38:38 UTC
The "fsck" binary itself is now part of util-linux-ng in rhel6 -ERic Created attachment 435077 [details]
fix fsck error handling
Doh.. Thanks Eric! Here's the patch.
Patch in comment #2 is from the partner who reported this, reviewed & localbuild tested by me. Fixed by upstream commit 6c6f2af9e3949197cf7a70255895a2f4451f2319. Thanks for the patch! Hmm, I'm a bit puzzled. I can't reproduce the original problem on older el6 versions now. Discussed this a bit with jmarko on irc but haven't had a chance to dig further. Upstream commit message: fsck: returns proper code on exec() error # fsck -t foo /dev/sda1; echo $? fsck: fsck.foo: not found /sbin/fsck: Error 2 while executing fsck.foo for /dev/sda1 0 new version: # fsck -t foo /dev/sda1; echo $? fsck: fsck.foo: not found fsck: Error 2 while executing fsck.foo for /dev/sda1 8 An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0699.html |