Bug 619139 - fsck returns zero instead of error code
Summary: fsck returns zero instead of error code
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: util-linux-ng
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Karel Zak
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-28 16:38 UTC by Bryn M. Reeves
Modified: 2018-11-14 19:19 UTC (History)
7 users (show)

(edit)
Clone Of: 618134
(edit)
Last Closed: 2011-05-19 14:05:51 UTC


Attachments (Terms of Use)
fix fsck error handling (1.63 KB, patch)
2010-07-28 16:59 UTC, Bryn M. Reeves
no flags Details | Diff


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0699 normal SHIPPED_LIVE util-linux-ng bug fix and enhancement update 2011-05-18 18:10:13 UTC

Description Bryn M. Reeves 2010-07-28 16:38:38 UTC
+++ This bug was initially created as a clone of Bug #618134 +++

Description of problem:
fsck command does not return with proper error code but returns zero under specific circumstance. The return value of fsck_device function should appear as the error code. 

Version-Release number of selected component (if applicable):
e2fsprogs-1.39-23.el5

How reproducible:
Always 

Steps to Reproduce:
1. Create entry such as following to /etc/fstab: 
    /dev/sda1  /data  ignore  defaults  1 2 ###fstype is "ignore"
2. Execute # fsck -t ignore /dev/sdb1 which would return error message. 
3. Execute echo $? to confirm it returned 0 instead of error code. 

  
Actual results:
# echo $? returns 0. 

Expected results:
It should return non-zero, desirably, 8. 

Additional info:
The bug has been encountered by vendor's middle ware, which continued to try running although there were an error.

Comment 1 Eric Sandeen 2010-07-28 16:49:08 UTC
The "fsck" binary itself is now part of util-linux-ng in rhel6

-ERic

Comment 2 Bryn M. Reeves 2010-07-28 16:59:28 UTC
Created attachment 435077 [details]
fix fsck error handling

Doh.. Thanks Eric! Here's the patch.

Comment 3 Bryn M. Reeves 2010-07-28 17:05:31 UTC
Patch in comment #2 is from the partner who reported this, reviewed & localbuild tested by me.

Comment 5 Karel Zak 2010-12-27 21:34:26 UTC
Fixed by upstream commit 6c6f2af9e3949197cf7a70255895a2f4451f2319. Thanks for the patch!

Comment 7 Bryn M. Reeves 2011-04-13 17:25:05 UTC
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.

Comment 8 Karel Zak 2011-04-13 23:03:39 UTC
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

Comment 12 errata-xmlrpc 2011-05-19 14:05:51 UTC
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


Note You need to log in before you can comment on or make changes to this bug.