krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
 Posted: Wed Jan 04, 2012 1:10 am Post subject: |
 |
|
You need to force nfsv3 to mount it with -o nfsvers=3,vers=3
the -t nfs was for nfsv3 and 2 and -t nfs4 for nfsv4, but now -t nfs == nfsv4 per default.
If you use a nfsv4 server (as it's the default now), then your mount point should have a root (define by fsid=0) and your mount point attach to it.
And the root mount point will be name /
So if /data is export as nfsv4 then your mount point is / and not /data
Here's my config, this might help you better seeing one working, note that /export/distfiles is use with version 3 while other use version 4
| Code: | # /etc/exports: NFS file systems being exported. See exports(5).
/export 192.168.0.0/24(rw,sec=sys,fsid=0,no_subtree_check,async,no_root_squash,nohide,anonuid=250,anongid=250)
/export/distfiles 192.168.0.0/24(rw,root_squash,no_subtree_check,nohide,anonuid=250,anongid=250,secure,nohide)
/export/kernel 192.168.0.0/24(rw,no_subtree_check,nohide)
/export/portageshare 192.168.0.0/24(rw,nohide,sync,all_squash,secure,no_subtree_check)
|
In nfsv3 you can mount it with server:/export/distfiles
In nfsv4 you can mount it with server:/distfiles (and /export is the nfs root that can be mount using server:/ )
and the fstab on the client
| Code: | faramir:/export/distfiles /mnt/faramir/distfiles nfs rw,users,nfsvers=3,vers=3 0 0
faramir:/portageshare /mnt/faramir/portageshare nfs4 rw,users 0 0
|
and the mount result
| Code: | mount | grep faramir
faramir:/export/distfiles on /mnt/faramir/distfiles type nfs (rw,users,noexec,nosuid,nodev,nfsvers=3,vers=3,addr=192.168.0.6)
faramir:/portageshare on /mnt/faramir/portageshare type nfs4 (rw,users,noexec,nosuid,nodev,addr=192.168.0.6,clientaddr=192.168.0.4)
|
You can then try
v3: mount -t nfs 192.168.1.3:/data /home/audiodef/Beethoven -o nfsvers=3,vers=3
or
v4: mount -t nfs4 192.168.1.3:/ /home/audiodef/Beethoven
I hope it will help you guys. |
|
Networking & Security
