mount.nfs: access denied by server while mounting on Ubuntu machines?How to resolve “mount.nfs: access denied by server” errorHow to fix ”mount.nfs: access denied …“ when trying to mount a NFS share exported by a Proxmox 5 machine?Ubuntu client wants to mount NFS share on old CentOS server: access denied by server while mountingSharing Mac Snow Leopard directory via NFSError when attempting to mount NFSv4 file systemAIX NFS mount.nfs: access denied by server while mountingWhere are NFS v4 logs under systemd?NFS + Kerberos: access denied by server while mountingnfs mount failed: reason given by server: No such file or directoryHow to fix ”mount.nfs: access denied …“ when trying to mount a NFS share exported by a Proxmox 5 machine?How to keep users with local sudo rights from having sudo rights on NFS file server?NFS client gets permission denied errorStale NFS File Handle why does fsid resolve it?
How can I prevent hyper evolved versions of regular creatures from wiping out their cousins?
Why is Minecraft giving an OpenGL error?
How does one intimidate enemies without having the capacity for violence?
Watching something be written to a file live with tail
Why is 150k or 200k jobs considered good when there's 300k+ births a month?
A case of the sniffles
Why is consensus so controversial in Britain?
High voltage LED indicator 40-1000 VDC without additional power supply
Rock identification in KY
Cross compiling for RPi - error while loading shared libraries
Today is the Center
Languages that we cannot (dis)prove to be Context-Free
What would happen to a modern skyscraper if it rains micro blackholes?
Codimension of non-flat locus
Revoked SSL certificate
Are astronomers waiting to see something in an image from a gravitational lens that they've already seen in an adjacent image?
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
Do infinite dimensional systems make sense?
Can a monk's single staff be considered dual wielded, as per the Dual Wielder feat?
Alternative to sending password over mail?
Why can't we play rap on piano?
Are the number of citations and number of published articles the most important criteria for a tenure promotion?
meaning of に in 本当に?
If human space travel is limited by the G force vulnerability, is there a way to counter G forces?
mount.nfs: access denied by server while mounting on Ubuntu machines?
How to resolve “mount.nfs: access denied by server” errorHow to fix ”mount.nfs: access denied …“ when trying to mount a NFS share exported by a Proxmox 5 machine?Ubuntu client wants to mount NFS share on old CentOS server: access denied by server while mountingSharing Mac Snow Leopard directory via NFSError when attempting to mount NFSv4 file systemAIX NFS mount.nfs: access denied by server while mountingWhere are NFS v4 logs under systemd?NFS + Kerberos: access denied by server while mountingnfs mount failed: reason given by server: No such file or directoryHow to fix ”mount.nfs: access denied …“ when trying to mount a NFS share exported by a Proxmox 5 machine?How to keep users with local sudo rights from having sudo rights on NFS file server?NFS client gets permission denied errorStale NFS File Handle why does fsid resolve it?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have three machines in production -
machineA 10.66.136.129
machineB 10.66.138.181
machineC 10.66.138.183
and all those machines have Ubuntu 12.04 installed in it and I have root access to all those three machines.
Now I am supposed to do below things in my above machines -
Create mount point /opt/exhibitor/conf
Mount the directory in all servers.
sudo mount <NFS-SERVER>:/opt/exhibitor/conf /opt/exhibitor/conf/
I have already created /opt/exhibitor/conf directory in all those three machines as mentioned above.
Now I am trying to create a Mount Point. So I followed the below process -
Install NFS support files and NFS kernel server in all the above three machines
$ sudo apt-get install nfs-common nfs-kernel-server
Create the shared directory in all the above three machines
$ mkdir /opt/exhibitor/conf/
Edited the /etc/exports and added the entry like this in all the above three machines -
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/opt/exhibitor/conf/ 10.66.136.129(rw)
/opt/exhibitor/conf/ 10.66.138.181(rw)
/opt/exhibitor/conf/ 10.66.138.183(rw)
I have tried mounting on machineA like below from machineB and machineC and it gives me this error-
root@machineB:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
root@machineC:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
Did my /etc/exports file looks good? I am pretty sure, I have messed up my exports file. As I have the same content in all the three machines in exports file.
Any idea what wrong I am doing here? And what will be the correct /exports file here?
linux ubuntu mount nfs
add a comment |
I have three machines in production -
machineA 10.66.136.129
machineB 10.66.138.181
machineC 10.66.138.183
and all those machines have Ubuntu 12.04 installed in it and I have root access to all those three machines.
Now I am supposed to do below things in my above machines -
Create mount point /opt/exhibitor/conf
Mount the directory in all servers.
sudo mount <NFS-SERVER>:/opt/exhibitor/conf /opt/exhibitor/conf/
I have already created /opt/exhibitor/conf directory in all those three machines as mentioned above.
Now I am trying to create a Mount Point. So I followed the below process -
Install NFS support files and NFS kernel server in all the above three machines
$ sudo apt-get install nfs-common nfs-kernel-server
Create the shared directory in all the above three machines
$ mkdir /opt/exhibitor/conf/
Edited the /etc/exports and added the entry like this in all the above three machines -
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/opt/exhibitor/conf/ 10.66.136.129(rw)
/opt/exhibitor/conf/ 10.66.138.181(rw)
/opt/exhibitor/conf/ 10.66.138.183(rw)
I have tried mounting on machineA like below from machineB and machineC and it gives me this error-
root@machineB:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
root@machineC:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
Did my /etc/exports file looks good? I am pretty sure, I have messed up my exports file. As I have the same content in all the three machines in exports file.
Any idea what wrong I am doing here? And what will be the correct /exports file here?
linux ubuntu mount nfs
1
FYI double check permissions on the host/client. If the NFS host has permissions0750or0700then the client trying to mount is very likely to fail with this same error message. I changed the host from0750to0755and then the error went away and all was well.
– Trevor Boyd Smith
Feb 28 '17 at 0:28
add a comment |
I have three machines in production -
machineA 10.66.136.129
machineB 10.66.138.181
machineC 10.66.138.183
and all those machines have Ubuntu 12.04 installed in it and I have root access to all those three machines.
Now I am supposed to do below things in my above machines -
Create mount point /opt/exhibitor/conf
Mount the directory in all servers.
sudo mount <NFS-SERVER>:/opt/exhibitor/conf /opt/exhibitor/conf/
I have already created /opt/exhibitor/conf directory in all those three machines as mentioned above.
Now I am trying to create a Mount Point. So I followed the below process -
Install NFS support files and NFS kernel server in all the above three machines
$ sudo apt-get install nfs-common nfs-kernel-server
Create the shared directory in all the above three machines
$ mkdir /opt/exhibitor/conf/
Edited the /etc/exports and added the entry like this in all the above three machines -
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/opt/exhibitor/conf/ 10.66.136.129(rw)
/opt/exhibitor/conf/ 10.66.138.181(rw)
/opt/exhibitor/conf/ 10.66.138.183(rw)
I have tried mounting on machineA like below from machineB and machineC and it gives me this error-
root@machineB:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
root@machineC:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
Did my /etc/exports file looks good? I am pretty sure, I have messed up my exports file. As I have the same content in all the three machines in exports file.
Any idea what wrong I am doing here? And what will be the correct /exports file here?
linux ubuntu mount nfs
I have three machines in production -
machineA 10.66.136.129
machineB 10.66.138.181
machineC 10.66.138.183
and all those machines have Ubuntu 12.04 installed in it and I have root access to all those three machines.
Now I am supposed to do below things in my above machines -
Create mount point /opt/exhibitor/conf
Mount the directory in all servers.
sudo mount <NFS-SERVER>:/opt/exhibitor/conf /opt/exhibitor/conf/
I have already created /opt/exhibitor/conf directory in all those three machines as mentioned above.
Now I am trying to create a Mount Point. So I followed the below process -
Install NFS support files and NFS kernel server in all the above three machines
$ sudo apt-get install nfs-common nfs-kernel-server
Create the shared directory in all the above three machines
$ mkdir /opt/exhibitor/conf/
Edited the /etc/exports and added the entry like this in all the above three machines -
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/opt/exhibitor/conf/ 10.66.136.129(rw)
/opt/exhibitor/conf/ 10.66.138.181(rw)
/opt/exhibitor/conf/ 10.66.138.183(rw)
I have tried mounting on machineA like below from machineB and machineC and it gives me this error-
root@machineB:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
root@machineC:/# sudo mount -t nfs 10.66.136.129:/opt/exhibitor/conf /opt/exhibitor/conf/
mount.nfs: access denied by server while mounting 10.66.136.129:/opt/exhibitor/conf
Did my /etc/exports file looks good? I am pretty sure, I have messed up my exports file. As I have the same content in all the three machines in exports file.
Any idea what wrong I am doing here? And what will be the correct /exports file here?
linux ubuntu mount nfs
linux ubuntu mount nfs
edited Aug 21 '18 at 8:19
Rui F Ribeiro
41.9k1483142
41.9k1483142
asked Dec 21 '13 at 7:51
arsenalarsenal
1,143152948
1,143152948
1
FYI double check permissions on the host/client. If the NFS host has permissions0750or0700then the client trying to mount is very likely to fail with this same error message. I changed the host from0750to0755and then the error went away and all was well.
– Trevor Boyd Smith
Feb 28 '17 at 0:28
add a comment |
1
FYI double check permissions on the host/client. If the NFS host has permissions0750or0700then the client trying to mount is very likely to fail with this same error message. I changed the host from0750to0755and then the error went away and all was well.
– Trevor Boyd Smith
Feb 28 '17 at 0:28
1
1
FYI double check permissions on the host/client. If the NFS host has permissions
0750 or 0700 then the client trying to mount is very likely to fail with this same error message. I changed the host from 0750 to 0755 and then the error went away and all was well.– Trevor Boyd Smith
Feb 28 '17 at 0:28
FYI double check permissions on the host/client. If the NFS host has permissions
0750 or 0700 then the client trying to mount is very likely to fail with this same error message. I changed the host from 0750 to 0755 and then the error went away and all was well.– Trevor Boyd Smith
Feb 28 '17 at 0:28
add a comment |
14 Answers
14
active
oldest
votes
exportfs
When you create a /etc/exports file on a server you need to make sure that you export it. Typically you'll want to run this command:
$ exportfs -a
This will export all the entries in the exports file.
showmount
The other thing I'll often do is from other machines I'll check any machine that's exporting NFS shares to the network using the showmount command.
$ showmount -e <NFS server name>
Example
Say for example I'm logged into scully.
$ showmount -e mulder
Export list for mulder:
/export/raid1/isos 192.168.1.0/24
/export/raid1/proj 192.168.1.0/24
/export/raid1/data 192.168.1.0/24
/export/raid1/home 192.168.1.0/24
/export/raid1/packages 192.168.1.0/24
fstab
To mount these upon boots you'd add this line to your client machines that want to consume the NFS mounts.
server:/shared/dir /opt/mounted/dir nfs rsize=8192,wsize=8192,timeo=14,intr
automounting
If you're going to be rebooting these servers then I highly suggest you look into setting up automounting (autofs) instead of adding these entries to /etc/fstab. It's a bit more work but is well worth the effort.
Doing so will allow you to reboot the servers more independently from one another and also will only create the NFS mount when it's actually needed and/or being used. When it goes idle it will get unmounted.
References
- 18.2. NFS Client Configuration - CentOS 5 Deployment Guide
Thanks for suggestion. I just did that and now it works fine. Instead of runningexportfs -a, I ranexportfs -rv. Is there any difference in between those? And in my case,showmount -e 10.66.136.129I will be doing from machineB and machineC. right?
– arsenal
Dec 21 '13 at 8:05
1
@TechGeeky - not really.exportfs -rvjust does a reexport + is verbose. The-awill export everything. As toshowmount -eyes you can run it from those machines or the one serving the shares.
– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
|
show 3 more comments
I saw the same error (mount.nfs: access denied by server while mounting...) and the issue was fixed by -o v3 option as follows:
$ sudo mount -o v3 a-nfs-server:/path/to/export /path/to/mount
- Server is Ubuntu 14.04 64bit LTS.
- Client is CentOS 6.5 64bit.
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
I tried this one and gotmount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)
– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
add a comment |
In my case works using nfs4 doing:
$ sudo mount -t nfs4 server-name:/ /path/to/mount
In the /etc/export file on server
/Path/to/export 192.168.1.0/24(rw,sync,fsid=0,no_root_squash,crossmnt,no_subtree_check,no_acl)
fsid=0 makes the /Path/to/export the root directory when you mount the share.
crossmnt, because I have some others drives in the exported file system that I want to access also.
no_root_squash, because I want to access as root user (su) from the client side. I'm pretty sure that I'm the only one that can do that in my local network.
Server and clients are Ubuntu 14.04 64bit.
If you want to use nfs3, the answer of @fumisky-wells works for me as well.
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
add a comment |
I was getting the same error message and my issue turned out to be due to the client machine having two network interfaces connected to the same LAN. The server had been configured to expect a specific IP address and traffic was going out on the second interface that has a dhcp IP address. So I just configured the second interface to have a static IP address and also added the second static IP address to the server configuration.
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
add a comment |
/etc/exports needs to be edited on the NFS server machine, not the clients, as you state you did, as it is checked by the NFS server when a client requests access to a share.
If you put the following in /etc/exports on the NFS server, it should work:
/opt/exhibitor/conf 10.66.136.129(rw)
/opt/exhibitor/conf 10.66.138.181(rw)
/opt/exhibitor/conf 10.66.138.183(rw)
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
@TechGeeky Did you reload the NFS exports after doing that, usingexportfs -a?
– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
|
show 2 more comments
If nfs-client is trying to mount exported share inside linux container then container should run in privileged mode.
In case of docker;
$ docker run -it --rm --privileged ubuntu:14.04
add a comment |
For me the problem was that I was using server's ip address in /etc/exports/ instead of the client one.
The thing is, you should put all the ips you grant access to on server's /etc/exports/
add a comment |
For me the problem was, that my router changed the used IP-address of the client, so that the entry in /etc/exports on the server machine allowed only access for an IP address which was not used any more.
add a comment |
Same thing could happen if you try to mount a NFS share on Virtual Box instance with network adapter configured as NAT.
Choosing Bridged Adapter in virtual machine network settings fixes this issue.
add a comment |
I know this is an old thread, but my problem had to do with LXC and AppArmor.
Killing AppArmor, or adding an exception profile, fixed it.
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
add a comment |
This error can also be caused by trying to mount an encrypted path. (For example in your home directory, if you chose to encrypt it)
add a comment |
The only solution that worked for me was to export filesystems starting with /srv. It looks like this is a limitation (or default option, at least) of NFSv4.
Since I was trying to export a USB drive that automounts to /media, I needed a way to get that 'mounted' under /srv. To accomplish that:
sudo mkdir /srv/videos
sudo mount --bind /media/jim/wdportable/videos /srv/videos
And in /etc/exports:
/srv/videos 192.168.0.200(ro)
When I exported /media/jim/wdportable/videos directly, attempting to mount on the client always resulted in mount.nfs: access denied by server.
The -o v3 solution worked, but I didn't want to force v3.
1
I can almost guarantee this would have been due to permissions on the/media/jimfolder. If the directory you're trying to share is (or is inside of) a dir with only700or750mode, NFS won't be able to traverse into it. If you changed/media/jimto751, it would probably work.
– Dale Anderson
2 days ago
add a comment |
It should be noted that a linked page that lead me here had my correct answer which was that you can NOT use * wildcard in IP address in the export. It is either * (all IP's) or used as a wildcard in domain names IE: *.domain.com.
Eg: this is correct
/Path/to/export 192.168.1.0/24(flags)
This won't work (or is incorrect at least), but worked for me for years until I tried mounting the export from a Fedora VM.
/Path/to/export 192.168.1.*(flags)
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
add a comment |
After battling with this same error message for hours, my problem turned out to be nothing more complicated than good old fashioned Linux file permissions on the NFS host.
The folder I was trying to share (/home/foo/app/share) had the correct permissions, but because the user's home directory (/home/foo) had 0750 mode on it, NFS wasn't able to traverse into it to access the shared dir.
As soon as I set the user's home directory to mode 0751, the NFS service was able to traverse into it and I was able to mount the share from my client machine.
add a comment |
protected by GAD3R Feb 18 '18 at 18:51
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
14 Answers
14
active
oldest
votes
14 Answers
14
active
oldest
votes
active
oldest
votes
active
oldest
votes
exportfs
When you create a /etc/exports file on a server you need to make sure that you export it. Typically you'll want to run this command:
$ exportfs -a
This will export all the entries in the exports file.
showmount
The other thing I'll often do is from other machines I'll check any machine that's exporting NFS shares to the network using the showmount command.
$ showmount -e <NFS server name>
Example
Say for example I'm logged into scully.
$ showmount -e mulder
Export list for mulder:
/export/raid1/isos 192.168.1.0/24
/export/raid1/proj 192.168.1.0/24
/export/raid1/data 192.168.1.0/24
/export/raid1/home 192.168.1.0/24
/export/raid1/packages 192.168.1.0/24
fstab
To mount these upon boots you'd add this line to your client machines that want to consume the NFS mounts.
server:/shared/dir /opt/mounted/dir nfs rsize=8192,wsize=8192,timeo=14,intr
automounting
If you're going to be rebooting these servers then I highly suggest you look into setting up automounting (autofs) instead of adding these entries to /etc/fstab. It's a bit more work but is well worth the effort.
Doing so will allow you to reboot the servers more independently from one another and also will only create the NFS mount when it's actually needed and/or being used. When it goes idle it will get unmounted.
References
- 18.2. NFS Client Configuration - CentOS 5 Deployment Guide
Thanks for suggestion. I just did that and now it works fine. Instead of runningexportfs -a, I ranexportfs -rv. Is there any difference in between those? And in my case,showmount -e 10.66.136.129I will be doing from machineB and machineC. right?
– arsenal
Dec 21 '13 at 8:05
1
@TechGeeky - not really.exportfs -rvjust does a reexport + is verbose. The-awill export everything. As toshowmount -eyes you can run it from those machines or the one serving the shares.
– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
|
show 3 more comments
exportfs
When you create a /etc/exports file on a server you need to make sure that you export it. Typically you'll want to run this command:
$ exportfs -a
This will export all the entries in the exports file.
showmount
The other thing I'll often do is from other machines I'll check any machine that's exporting NFS shares to the network using the showmount command.
$ showmount -e <NFS server name>
Example
Say for example I'm logged into scully.
$ showmount -e mulder
Export list for mulder:
/export/raid1/isos 192.168.1.0/24
/export/raid1/proj 192.168.1.0/24
/export/raid1/data 192.168.1.0/24
/export/raid1/home 192.168.1.0/24
/export/raid1/packages 192.168.1.0/24
fstab
To mount these upon boots you'd add this line to your client machines that want to consume the NFS mounts.
server:/shared/dir /opt/mounted/dir nfs rsize=8192,wsize=8192,timeo=14,intr
automounting
If you're going to be rebooting these servers then I highly suggest you look into setting up automounting (autofs) instead of adding these entries to /etc/fstab. It's a bit more work but is well worth the effort.
Doing so will allow you to reboot the servers more independently from one another and also will only create the NFS mount when it's actually needed and/or being used. When it goes idle it will get unmounted.
References
- 18.2. NFS Client Configuration - CentOS 5 Deployment Guide
Thanks for suggestion. I just did that and now it works fine. Instead of runningexportfs -a, I ranexportfs -rv. Is there any difference in between those? And in my case,showmount -e 10.66.136.129I will be doing from machineB and machineC. right?
– arsenal
Dec 21 '13 at 8:05
1
@TechGeeky - not really.exportfs -rvjust does a reexport + is verbose. The-awill export everything. As toshowmount -eyes you can run it from those machines or the one serving the shares.
– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
|
show 3 more comments
exportfs
When you create a /etc/exports file on a server you need to make sure that you export it. Typically you'll want to run this command:
$ exportfs -a
This will export all the entries in the exports file.
showmount
The other thing I'll often do is from other machines I'll check any machine that's exporting NFS shares to the network using the showmount command.
$ showmount -e <NFS server name>
Example
Say for example I'm logged into scully.
$ showmount -e mulder
Export list for mulder:
/export/raid1/isos 192.168.1.0/24
/export/raid1/proj 192.168.1.0/24
/export/raid1/data 192.168.1.0/24
/export/raid1/home 192.168.1.0/24
/export/raid1/packages 192.168.1.0/24
fstab
To mount these upon boots you'd add this line to your client machines that want to consume the NFS mounts.
server:/shared/dir /opt/mounted/dir nfs rsize=8192,wsize=8192,timeo=14,intr
automounting
If you're going to be rebooting these servers then I highly suggest you look into setting up automounting (autofs) instead of adding these entries to /etc/fstab. It's a bit more work but is well worth the effort.
Doing so will allow you to reboot the servers more independently from one another and also will only create the NFS mount when it's actually needed and/or being used. When it goes idle it will get unmounted.
References
- 18.2. NFS Client Configuration - CentOS 5 Deployment Guide
exportfs
When you create a /etc/exports file on a server you need to make sure that you export it. Typically you'll want to run this command:
$ exportfs -a
This will export all the entries in the exports file.
showmount
The other thing I'll often do is from other machines I'll check any machine that's exporting NFS shares to the network using the showmount command.
$ showmount -e <NFS server name>
Example
Say for example I'm logged into scully.
$ showmount -e mulder
Export list for mulder:
/export/raid1/isos 192.168.1.0/24
/export/raid1/proj 192.168.1.0/24
/export/raid1/data 192.168.1.0/24
/export/raid1/home 192.168.1.0/24
/export/raid1/packages 192.168.1.0/24
fstab
To mount these upon boots you'd add this line to your client machines that want to consume the NFS mounts.
server:/shared/dir /opt/mounted/dir nfs rsize=8192,wsize=8192,timeo=14,intr
automounting
If you're going to be rebooting these servers then I highly suggest you look into setting up automounting (autofs) instead of adding these entries to /etc/fstab. It's a bit more work but is well worth the effort.
Doing so will allow you to reboot the servers more independently from one another and also will only create the NFS mount when it's actually needed and/or being used. When it goes idle it will get unmounted.
References
- 18.2. NFS Client Configuration - CentOS 5 Deployment Guide
edited Dec 21 '13 at 8:23
answered Dec 21 '13 at 7:58
slm♦slm
255k71541687
255k71541687
Thanks for suggestion. I just did that and now it works fine. Instead of runningexportfs -a, I ranexportfs -rv. Is there any difference in between those? And in my case,showmount -e 10.66.136.129I will be doing from machineB and machineC. right?
– arsenal
Dec 21 '13 at 8:05
1
@TechGeeky - not really.exportfs -rvjust does a reexport + is verbose. The-awill export everything. As toshowmount -eyes you can run it from those machines or the one serving the shares.
– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
|
show 3 more comments
Thanks for suggestion. I just did that and now it works fine. Instead of runningexportfs -a, I ranexportfs -rv. Is there any difference in between those? And in my case,showmount -e 10.66.136.129I will be doing from machineB and machineC. right?
– arsenal
Dec 21 '13 at 8:05
1
@TechGeeky - not really.exportfs -rvjust does a reexport + is verbose. The-awill export everything. As toshowmount -eyes you can run it from those machines or the one serving the shares.
– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
Thanks for suggestion. I just did that and now it works fine. Instead of running
exportfs -a, I ran exportfs -rv. Is there any difference in between those? And in my case, showmount -e 10.66.136.129 I will be doing from machineB and machineC. right?– arsenal
Dec 21 '13 at 8:05
Thanks for suggestion. I just did that and now it works fine. Instead of running
exportfs -a, I ran exportfs -rv. Is there any difference in between those? And in my case, showmount -e 10.66.136.129 I will be doing from machineB and machineC. right?– arsenal
Dec 21 '13 at 8:05
1
1
@TechGeeky - not really.
exportfs -rv just does a reexport + is verbose. The -a will export everything. As to showmount -e yes you can run it from those machines or the one serving the shares.– slm♦
Dec 21 '13 at 8:08
@TechGeeky - not really.
exportfs -rv just does a reexport + is verbose. The -a will export everything. As to showmount -e yes you can run it from those machines or the one serving the shares.– slm♦
Dec 21 '13 at 8:08
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
ok.. Thanks, makese sense now.. One last thing. I believe there is one more thing to this mount point thing, fstab file.. correct? Now which machine fstab file, I am supposed to modify? And what content I am supposed to add in there? Any idea?
– arsenal
Dec 21 '13 at 8:13
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
@TechGeeky see updates. You add entries to the clients that want to consume the NFS shares.
– slm♦
Dec 21 '13 at 8:15
1
1
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
On Ubuntu, you must first install nfs-kernel-server for exportfs to be available. Source: manpages.ubuntu.com/manpages/trusty/man8/exportfs.8.html
– flickerfly
Jun 5 '15 at 18:36
|
show 3 more comments
I saw the same error (mount.nfs: access denied by server while mounting...) and the issue was fixed by -o v3 option as follows:
$ sudo mount -o v3 a-nfs-server:/path/to/export /path/to/mount
- Server is Ubuntu 14.04 64bit LTS.
- Client is CentOS 6.5 64bit.
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
I tried this one and gotmount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)
– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
add a comment |
I saw the same error (mount.nfs: access denied by server while mounting...) and the issue was fixed by -o v3 option as follows:
$ sudo mount -o v3 a-nfs-server:/path/to/export /path/to/mount
- Server is Ubuntu 14.04 64bit LTS.
- Client is CentOS 6.5 64bit.
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
I tried this one and gotmount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)
– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
add a comment |
I saw the same error (mount.nfs: access denied by server while mounting...) and the issue was fixed by -o v3 option as follows:
$ sudo mount -o v3 a-nfs-server:/path/to/export /path/to/mount
- Server is Ubuntu 14.04 64bit LTS.
- Client is CentOS 6.5 64bit.
I saw the same error (mount.nfs: access denied by server while mounting...) and the issue was fixed by -o v3 option as follows:
$ sudo mount -o v3 a-nfs-server:/path/to/export /path/to/mount
- Server is Ubuntu 14.04 64bit LTS.
- Client is CentOS 6.5 64bit.
edited Aug 12 '14 at 5:39
HalosGhost
3,78392236
3,78392236
answered Aug 12 '14 at 5:09
Fumisky WellsFumisky Wells
41144
41144
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
I tried this one and gotmount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)
– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
add a comment |
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
I tried this one and gotmount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)
– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
2
2
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
None of the rest helped, this was the solution, in my case.
– Urhixidur
Mar 7 '16 at 17:34
1
1
I tried this one and got
mount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)– Steve
Jul 13 '16 at 11:28
I tried this one and got
mount.nfs: Connection timed out. (Client is Ubuntu 14.04 LTS 64-bit. Server is a QNAP NFS with QTS 4.0.2 2016/01/09.)– Steve
Jul 13 '16 at 11:28
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
Yep, when I upgraded my server to Ubuntu 16 this was what the problem and solution was.
– user7000
Dec 20 '16 at 18:02
2
2
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
Be careful with this. NFSv3 is ancient and long obsolete; it really shouldn't be used anymore (and this was even true when this post was written).
– Michael Hampton
Jan 31 '18 at 20:23
add a comment |
In my case works using nfs4 doing:
$ sudo mount -t nfs4 server-name:/ /path/to/mount
In the /etc/export file on server
/Path/to/export 192.168.1.0/24(rw,sync,fsid=0,no_root_squash,crossmnt,no_subtree_check,no_acl)
fsid=0 makes the /Path/to/export the root directory when you mount the share.
crossmnt, because I have some others drives in the exported file system that I want to access also.
no_root_squash, because I want to access as root user (su) from the client side. I'm pretty sure that I'm the only one that can do that in my local network.
Server and clients are Ubuntu 14.04 64bit.
If you want to use nfs3, the answer of @fumisky-wells works for me as well.
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
add a comment |
In my case works using nfs4 doing:
$ sudo mount -t nfs4 server-name:/ /path/to/mount
In the /etc/export file on server
/Path/to/export 192.168.1.0/24(rw,sync,fsid=0,no_root_squash,crossmnt,no_subtree_check,no_acl)
fsid=0 makes the /Path/to/export the root directory when you mount the share.
crossmnt, because I have some others drives in the exported file system that I want to access also.
no_root_squash, because I want to access as root user (su) from the client side. I'm pretty sure that I'm the only one that can do that in my local network.
Server and clients are Ubuntu 14.04 64bit.
If you want to use nfs3, the answer of @fumisky-wells works for me as well.
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
add a comment |
In my case works using nfs4 doing:
$ sudo mount -t nfs4 server-name:/ /path/to/mount
In the /etc/export file on server
/Path/to/export 192.168.1.0/24(rw,sync,fsid=0,no_root_squash,crossmnt,no_subtree_check,no_acl)
fsid=0 makes the /Path/to/export the root directory when you mount the share.
crossmnt, because I have some others drives in the exported file system that I want to access also.
no_root_squash, because I want to access as root user (su) from the client side. I'm pretty sure that I'm the only one that can do that in my local network.
Server and clients are Ubuntu 14.04 64bit.
If you want to use nfs3, the answer of @fumisky-wells works for me as well.
In my case works using nfs4 doing:
$ sudo mount -t nfs4 server-name:/ /path/to/mount
In the /etc/export file on server
/Path/to/export 192.168.1.0/24(rw,sync,fsid=0,no_root_squash,crossmnt,no_subtree_check,no_acl)
fsid=0 makes the /Path/to/export the root directory when you mount the share.
crossmnt, because I have some others drives in the exported file system that I want to access also.
no_root_squash, because I want to access as root user (su) from the client side. I'm pretty sure that I'm the only one that can do that in my local network.
Server and clients are Ubuntu 14.04 64bit.
If you want to use nfs3, the answer of @fumisky-wells works for me as well.
answered Aug 20 '14 at 12:27
victevicte
7112
7112
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
add a comment |
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
You earned yourself an upvote sir; I have a NAS, so modding the /etc/export file isn't an option, but specifying the complete path did the trick. well done.
– MDMoore313
Dec 18 '14 at 1:19
add a comment |
I was getting the same error message and my issue turned out to be due to the client machine having two network interfaces connected to the same LAN. The server had been configured to expect a specific IP address and traffic was going out on the second interface that has a dhcp IP address. So I just configured the second interface to have a static IP address and also added the second static IP address to the server configuration.
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
add a comment |
I was getting the same error message and my issue turned out to be due to the client machine having two network interfaces connected to the same LAN. The server had been configured to expect a specific IP address and traffic was going out on the second interface that has a dhcp IP address. So I just configured the second interface to have a static IP address and also added the second static IP address to the server configuration.
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
add a comment |
I was getting the same error message and my issue turned out to be due to the client machine having two network interfaces connected to the same LAN. The server had been configured to expect a specific IP address and traffic was going out on the second interface that has a dhcp IP address. So I just configured the second interface to have a static IP address and also added the second static IP address to the server configuration.
I was getting the same error message and my issue turned out to be due to the client machine having two network interfaces connected to the same LAN. The server had been configured to expect a specific IP address and traffic was going out on the second interface that has a dhcp IP address. So I just configured the second interface to have a static IP address and also added the second static IP address to the server configuration.
answered Aug 16 '16 at 2:46
majjinatormajjinator
411
411
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
add a comment |
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
Man I wish this was more towards the top, that's exactly what was happening in my case
– Brian Leishman
Mar 28 at 16:16
add a comment |
/etc/exports needs to be edited on the NFS server machine, not the clients, as you state you did, as it is checked by the NFS server when a client requests access to a share.
If you put the following in /etc/exports on the NFS server, it should work:
/opt/exhibitor/conf 10.66.136.129(rw)
/opt/exhibitor/conf 10.66.138.181(rw)
/opt/exhibitor/conf 10.66.138.183(rw)
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
@TechGeeky Did you reload the NFS exports after doing that, usingexportfs -a?
– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
|
show 2 more comments
/etc/exports needs to be edited on the NFS server machine, not the clients, as you state you did, as it is checked by the NFS server when a client requests access to a share.
If you put the following in /etc/exports on the NFS server, it should work:
/opt/exhibitor/conf 10.66.136.129(rw)
/opt/exhibitor/conf 10.66.138.181(rw)
/opt/exhibitor/conf 10.66.138.183(rw)
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
@TechGeeky Did you reload the NFS exports after doing that, usingexportfs -a?
– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
|
show 2 more comments
/etc/exports needs to be edited on the NFS server machine, not the clients, as you state you did, as it is checked by the NFS server when a client requests access to a share.
If you put the following in /etc/exports on the NFS server, it should work:
/opt/exhibitor/conf 10.66.136.129(rw)
/opt/exhibitor/conf 10.66.138.181(rw)
/opt/exhibitor/conf 10.66.138.183(rw)
/etc/exports needs to be edited on the NFS server machine, not the clients, as you state you did, as it is checked by the NFS server when a client requests access to a share.
If you put the following in /etc/exports on the NFS server, it should work:
/opt/exhibitor/conf 10.66.136.129(rw)
/opt/exhibitor/conf 10.66.138.181(rw)
/opt/exhibitor/conf 10.66.138.183(rw)
answered Dec 21 '13 at 7:53
Chris DownChris Down
81.6k15190204
81.6k15190204
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
@TechGeeky Did you reload the NFS exports after doing that, usingexportfs -a?
– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
|
show 2 more comments
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
@TechGeeky Did you reload the NFS exports after doing that, usingexportfs -a?
– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
I already have this in my exports file on machineA. And then I am mounting it from machineB and machineC and it doesn't work somehow.. Is it possible I have added same information in all the three machines in exports file, will that be a problem? I should be adding only in machineA?
– arsenal
Dec 21 '13 at 7:56
1
1
@TechGeeky Did you reload the NFS exports after doing that, using
exportfs -a?– Chris Down
Dec 21 '13 at 7:58
@TechGeeky Did you reload the NFS exports after doing that, using
exportfs -a?– Chris Down
Dec 21 '13 at 7:58
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
I just did that and now it works fine. I am trying to understand this whole thing in better way, so my first question is, machineA is NFS server and machineB and machineC are clients.. Correct? Second question is, if machineA is my NFS server, then only in the /etc/exports file of machineA, I will be adding the above three lines as you mentioned in your solution and we won't touch exports file of machineB and machineC? Correct?
– arsenal
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
@TechGeeky As long as you are mounting a share on machine A, then that's correct in both cases.
– Chris Down
Dec 21 '13 at 8:04
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
Thanks. Now I understand this much better. Why I have asked this question because I also have similar stuff in staging environment. And what I did in those three machines in staging environment, I added same three lines in all my /etc/exports files of three machines instead of adding it only in machineA but still it works fine. And now I have understood the whole concept more clearly. Thanks for the help.
– arsenal
Dec 21 '13 at 8:08
|
show 2 more comments
If nfs-client is trying to mount exported share inside linux container then container should run in privileged mode.
In case of docker;
$ docker run -it --rm --privileged ubuntu:14.04
add a comment |
If nfs-client is trying to mount exported share inside linux container then container should run in privileged mode.
In case of docker;
$ docker run -it --rm --privileged ubuntu:14.04
add a comment |
If nfs-client is trying to mount exported share inside linux container then container should run in privileged mode.
In case of docker;
$ docker run -it --rm --privileged ubuntu:14.04
If nfs-client is trying to mount exported share inside linux container then container should run in privileged mode.
In case of docker;
$ docker run -it --rm --privileged ubuntu:14.04
answered May 5 '16 at 15:36
efesaidefesaid
1772
1772
add a comment |
add a comment |
For me the problem was that I was using server's ip address in /etc/exports/ instead of the client one.
The thing is, you should put all the ips you grant access to on server's /etc/exports/
add a comment |
For me the problem was that I was using server's ip address in /etc/exports/ instead of the client one.
The thing is, you should put all the ips you grant access to on server's /etc/exports/
add a comment |
For me the problem was that I was using server's ip address in /etc/exports/ instead of the client one.
The thing is, you should put all the ips you grant access to on server's /etc/exports/
For me the problem was that I was using server's ip address in /etc/exports/ instead of the client one.
The thing is, you should put all the ips you grant access to on server's /etc/exports/
answered Sep 1 '16 at 20:29
VanuanVanuan
1213
1213
add a comment |
add a comment |
For me the problem was, that my router changed the used IP-address of the client, so that the entry in /etc/exports on the server machine allowed only access for an IP address which was not used any more.
add a comment |
For me the problem was, that my router changed the used IP-address of the client, so that the entry in /etc/exports on the server machine allowed only access for an IP address which was not used any more.
add a comment |
For me the problem was, that my router changed the used IP-address of the client, so that the entry in /etc/exports on the server machine allowed only access for an IP address which was not used any more.
For me the problem was, that my router changed the used IP-address of the client, so that the entry in /etc/exports on the server machine allowed only access for an IP address which was not used any more.
answered Aug 9 '16 at 7:55
AlexAlex
4021515
4021515
add a comment |
add a comment |
Same thing could happen if you try to mount a NFS share on Virtual Box instance with network adapter configured as NAT.
Choosing Bridged Adapter in virtual machine network settings fixes this issue.
add a comment |
Same thing could happen if you try to mount a NFS share on Virtual Box instance with network adapter configured as NAT.
Choosing Bridged Adapter in virtual machine network settings fixes this issue.
add a comment |
Same thing could happen if you try to mount a NFS share on Virtual Box instance with network adapter configured as NAT.
Choosing Bridged Adapter in virtual machine network settings fixes this issue.
Same thing could happen if you try to mount a NFS share on Virtual Box instance with network adapter configured as NAT.
Choosing Bridged Adapter in virtual machine network settings fixes this issue.
answered Sep 29 '16 at 7:04
mkapturmkaptur
11
11
add a comment |
add a comment |
I know this is an old thread, but my problem had to do with LXC and AppArmor.
Killing AppArmor, or adding an exception profile, fixed it.
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
add a comment |
I know this is an old thread, but my problem had to do with LXC and AppArmor.
Killing AppArmor, or adding an exception profile, fixed it.
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
add a comment |
I know this is an old thread, but my problem had to do with LXC and AppArmor.
Killing AppArmor, or adding an exception profile, fixed it.
I know this is an old thread, but my problem had to do with LXC and AppArmor.
Killing AppArmor, or adding an exception profile, fixed it.
edited Mar 30 '17 at 6:41
lgeorget
9,11622653
9,11622653
answered Mar 30 '17 at 2:31
JoshJosh
1
1
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
add a comment |
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox
– myrdd
Jun 17 '18 at 11:59
add a comment |
This error can also be caused by trying to mount an encrypted path. (For example in your home directory, if you chose to encrypt it)
add a comment |
This error can also be caused by trying to mount an encrypted path. (For example in your home directory, if you chose to encrypt it)
add a comment |
This error can also be caused by trying to mount an encrypted path. (For example in your home directory, if you chose to encrypt it)
This error can also be caused by trying to mount an encrypted path. (For example in your home directory, if you chose to encrypt it)
answered Jan 19 '18 at 8:35
user3737396user3737396
1
1
add a comment |
add a comment |
The only solution that worked for me was to export filesystems starting with /srv. It looks like this is a limitation (or default option, at least) of NFSv4.
Since I was trying to export a USB drive that automounts to /media, I needed a way to get that 'mounted' under /srv. To accomplish that:
sudo mkdir /srv/videos
sudo mount --bind /media/jim/wdportable/videos /srv/videos
And in /etc/exports:
/srv/videos 192.168.0.200(ro)
When I exported /media/jim/wdportable/videos directly, attempting to mount on the client always resulted in mount.nfs: access denied by server.
The -o v3 solution worked, but I didn't want to force v3.
1
I can almost guarantee this would have been due to permissions on the/media/jimfolder. If the directory you're trying to share is (or is inside of) a dir with only700or750mode, NFS won't be able to traverse into it. If you changed/media/jimto751, it would probably work.
– Dale Anderson
2 days ago
add a comment |
The only solution that worked for me was to export filesystems starting with /srv. It looks like this is a limitation (or default option, at least) of NFSv4.
Since I was trying to export a USB drive that automounts to /media, I needed a way to get that 'mounted' under /srv. To accomplish that:
sudo mkdir /srv/videos
sudo mount --bind /media/jim/wdportable/videos /srv/videos
And in /etc/exports:
/srv/videos 192.168.0.200(ro)
When I exported /media/jim/wdportable/videos directly, attempting to mount on the client always resulted in mount.nfs: access denied by server.
The -o v3 solution worked, but I didn't want to force v3.
1
I can almost guarantee this would have been due to permissions on the/media/jimfolder. If the directory you're trying to share is (or is inside of) a dir with only700or750mode, NFS won't be able to traverse into it. If you changed/media/jimto751, it would probably work.
– Dale Anderson
2 days ago
add a comment |
The only solution that worked for me was to export filesystems starting with /srv. It looks like this is a limitation (or default option, at least) of NFSv4.
Since I was trying to export a USB drive that automounts to /media, I needed a way to get that 'mounted' under /srv. To accomplish that:
sudo mkdir /srv/videos
sudo mount --bind /media/jim/wdportable/videos /srv/videos
And in /etc/exports:
/srv/videos 192.168.0.200(ro)
When I exported /media/jim/wdportable/videos directly, attempting to mount on the client always resulted in mount.nfs: access denied by server.
The -o v3 solution worked, but I didn't want to force v3.
The only solution that worked for me was to export filesystems starting with /srv. It looks like this is a limitation (or default option, at least) of NFSv4.
Since I was trying to export a USB drive that automounts to /media, I needed a way to get that 'mounted' under /srv. To accomplish that:
sudo mkdir /srv/videos
sudo mount --bind /media/jim/wdportable/videos /srv/videos
And in /etc/exports:
/srv/videos 192.168.0.200(ro)
When I exported /media/jim/wdportable/videos directly, attempting to mount on the client always resulted in mount.nfs: access denied by server.
The -o v3 solution worked, but I didn't want to force v3.
answered Feb 6 '18 at 5:28
Jim StewartJim Stewart
29017
29017
1
I can almost guarantee this would have been due to permissions on the/media/jimfolder. If the directory you're trying to share is (or is inside of) a dir with only700or750mode, NFS won't be able to traverse into it. If you changed/media/jimto751, it would probably work.
– Dale Anderson
2 days ago
add a comment |
1
I can almost guarantee this would have been due to permissions on the/media/jimfolder. If the directory you're trying to share is (or is inside of) a dir with only700or750mode, NFS won't be able to traverse into it. If you changed/media/jimto751, it would probably work.
– Dale Anderson
2 days ago
1
1
I can almost guarantee this would have been due to permissions on the
/media/jim folder. If the directory you're trying to share is (or is inside of) a dir with only 700 or 750 mode, NFS won't be able to traverse into it. If you changed /media/jim to 751, it would probably work.– Dale Anderson
2 days ago
I can almost guarantee this would have been due to permissions on the
/media/jim folder. If the directory you're trying to share is (or is inside of) a dir with only 700 or 750 mode, NFS won't be able to traverse into it. If you changed /media/jim to 751, it would probably work.– Dale Anderson
2 days ago
add a comment |
It should be noted that a linked page that lead me here had my correct answer which was that you can NOT use * wildcard in IP address in the export. It is either * (all IP's) or used as a wildcard in domain names IE: *.domain.com.
Eg: this is correct
/Path/to/export 192.168.1.0/24(flags)
This won't work (or is incorrect at least), but worked for me for years until I tried mounting the export from a Fedora VM.
/Path/to/export 192.168.1.*(flags)
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
add a comment |
It should be noted that a linked page that lead me here had my correct answer which was that you can NOT use * wildcard in IP address in the export. It is either * (all IP's) or used as a wildcard in domain names IE: *.domain.com.
Eg: this is correct
/Path/to/export 192.168.1.0/24(flags)
This won't work (or is incorrect at least), but worked for me for years until I tried mounting the export from a Fedora VM.
/Path/to/export 192.168.1.*(flags)
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
add a comment |
It should be noted that a linked page that lead me here had my correct answer which was that you can NOT use * wildcard in IP address in the export. It is either * (all IP's) or used as a wildcard in domain names IE: *.domain.com.
Eg: this is correct
/Path/to/export 192.168.1.0/24(flags)
This won't work (or is incorrect at least), but worked for me for years until I tried mounting the export from a Fedora VM.
/Path/to/export 192.168.1.*(flags)
It should be noted that a linked page that lead me here had my correct answer which was that you can NOT use * wildcard in IP address in the export. It is either * (all IP's) or used as a wildcard in domain names IE: *.domain.com.
Eg: this is correct
/Path/to/export 192.168.1.0/24(flags)
This won't work (or is incorrect at least), but worked for me for years until I tried mounting the export from a Fedora VM.
/Path/to/export 192.168.1.*(flags)
answered Feb 7 '18 at 6:23
FreeSoftwareServersFreeSoftwareServers
1,02931941
1,02931941
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
add a comment |
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
unix.stackexchange.com/questions/106122/…
– FreeSoftwareServers
Feb 7 '18 at 6:24
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
I think the reason it failed is possibly NFSv4 because I know Fedora is bleeding edge new stuff and my old VM's worked fine but probably used older NFS version. Just a guess.
– FreeSoftwareServers
Feb 7 '18 at 6:25
add a comment |
After battling with this same error message for hours, my problem turned out to be nothing more complicated than good old fashioned Linux file permissions on the NFS host.
The folder I was trying to share (/home/foo/app/share) had the correct permissions, but because the user's home directory (/home/foo) had 0750 mode on it, NFS wasn't able to traverse into it to access the shared dir.
As soon as I set the user's home directory to mode 0751, the NFS service was able to traverse into it and I was able to mount the share from my client machine.
add a comment |
After battling with this same error message for hours, my problem turned out to be nothing more complicated than good old fashioned Linux file permissions on the NFS host.
The folder I was trying to share (/home/foo/app/share) had the correct permissions, but because the user's home directory (/home/foo) had 0750 mode on it, NFS wasn't able to traverse into it to access the shared dir.
As soon as I set the user's home directory to mode 0751, the NFS service was able to traverse into it and I was able to mount the share from my client machine.
add a comment |
After battling with this same error message for hours, my problem turned out to be nothing more complicated than good old fashioned Linux file permissions on the NFS host.
The folder I was trying to share (/home/foo/app/share) had the correct permissions, but because the user's home directory (/home/foo) had 0750 mode on it, NFS wasn't able to traverse into it to access the shared dir.
As soon as I set the user's home directory to mode 0751, the NFS service was able to traverse into it and I was able to mount the share from my client machine.
After battling with this same error message for hours, my problem turned out to be nothing more complicated than good old fashioned Linux file permissions on the NFS host.
The folder I was trying to share (/home/foo/app/share) had the correct permissions, but because the user's home directory (/home/foo) had 0750 mode on it, NFS wasn't able to traverse into it to access the shared dir.
As soon as I set the user's home directory to mode 0751, the NFS service was able to traverse into it and I was able to mount the share from my client machine.
answered 2 days ago
Dale AndersonDale Anderson
33128
33128
add a comment |
add a comment |
protected by GAD3R Feb 18 '18 at 18:51
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
FYI double check permissions on the host/client. If the NFS host has permissions
0750or0700then the client trying to mount is very likely to fail with this same error message. I changed the host from0750to0755and then the error went away and all was well.– Trevor Boyd Smith
Feb 28 '17 at 0:28