Bug 150858 - bad interaction nfsv4 autofs
Summary: bad interaction nfsv4 autofs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Moyer
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-11 14:03 UTC by Neal Becker
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-03-11 19:07:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Neal Becker 2005-03-11 14:03:47 UTC
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:
Always

Steps to Reproduce:
1. ls ~nbecker
2.
3.
    

Additional info:

Comment 1 Jeff Moyer 2005-03-11 19:07:14 UTC
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 19:09:44 UTC
You misunderstood me.  With nfs4 it did NOT do a bind mount. 

Comment 3 Jeff Moyer 2005-03-11 19:21:19 UTC
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.