Bug 150858 - bad interaction nfsv4 autofs
bad interaction nfsv4 autofs
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Moyer
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-03-11 09:03 EST by Neal Becker
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-03-11 14:07:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neal Becker 2005-03-11 09:03:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
autofs has this map:
nbecker         -fstype=nfs4 rpppc1.md.hnsnet:/disk1/nbecker

When rpppc1.md.hnsnet is the client, it doesn't work correctly.  Without -fstype=nfs4, this will result in the following mount:
/disk1/nbecker on /home/nbecker type none (rw,bind)

But with -fstype=nfs4, it isn't a bind mount, it is nfs4.

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

How reproducible:

Steps to Reproduce:
1. ls ~nbecker

Additional info:
Comment 1 Jeff Moyer 2005-03-11 14:07:14 EST
This is working as it should.  When it is a local file system, autofs simply
does a bind mount.  If you don't want it to do this, then you can either stick
with your solution (adding -fstype to the options), or you can specify -nosymlink.
Comment 2 Neal Becker 2005-03-11 14:09:44 EST
You misunderstood me.  With nfs4 it did NOT do a bind mount. 
Comment 3 Jeff Moyer 2005-03-11 14:21:19 EST
That is correct behaviour.  If you believe it is not correct, then point to the
documentation which states otherwise.

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