Bug 465966 - mount.nfs returns incorrect exit code for failed mount
mount.nfs returns incorrect exit code for failed mount
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: nfs-utils (Show other bugs)
All Linux
urgent Severity urgent
: beta
: ---
Assigned To: Steve Dickson
Martin Jenner
: Regression
Depends On:
  Show dependency treegraph
Reported: 2008-10-07 09:49 EDT by Jeff Moyer
Modified: 2009-01-20 16:01 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 16:01:09 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (1.11 KB, patch)
2008-10-07 10:21 EDT, Steve Dickson
no flags Details | Diff

  None (edit)
Description Jeff Moyer 2008-10-07 09:49:07 EDT
Description of problem:
If you try to mount an export that is not exported to the client, you get an error message of permission denied, but mount returns exit code 0, indicating success.  This breaks the automounter, which needs to know that the mount failed.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
See problem description.
I will also check to see if the autofs rhts tests will catch this.
Comment 1 Steve Dickson 2008-10-07 10:11:42 EDT
It seem the regression happen with the fix to
Comment 2 Steve Dickson 2008-10-07 10:21:14 EDT
Created attachment 319642 [details]
Proposed patch
Comment 3 Steve Dickson 2008-10-07 10:48:07 EDT
Fixed in nfs-utils-1.0.9-38.el5
Comment 5 Jeff Moyer 2008-10-07 10:58:20 EDT
I tested the updated package and found that:
1) it returns exit code 32 for the permission denied case
2) it returns success when it successfully mounts
3) automount behaviour has returned to normal.

Comment 8 errata-xmlrpc 2009-01-20 16:01:09 EST
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.


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