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;








57















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?










share|improve this question



















  • 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

















57















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?










share|improve this question



















  • 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













57












57








57


25






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?










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








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 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












  • 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







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










14 Answers
14






active

oldest

votes


















62














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





share|improve this answer

























  • 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





    @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











  • @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


















31














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.





share|improve this answer




















  • 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 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






  • 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


















7














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.






share|improve this answer























  • 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


















4














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.






share|improve this answer























  • 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


















2














/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)





share|improve this answer























  • 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, 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











  • @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


















2














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






share|improve this answer






























    2














    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/






    share|improve this answer






























      0














      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.






      share|improve this answer






























        0














        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.






        share|improve this answer






























          0














          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.






          share|improve this answer

























          • see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox

            – myrdd
            Jun 17 '18 at 11:59


















          0














          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)






          share|improve this answer






























            0














            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.






            share|improve this answer


















            • 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


















            0














            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)





            share|improve this answer























            • 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


















            0














            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.






            share|improve this answer





















              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









              62














              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





              share|improve this answer

























              • 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





                @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











              • @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















              62














              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





              share|improve this answer

























              • 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





                @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











              • @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













              62












              62








              62







              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





              share|improve this answer















              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






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Dec 21 '13 at 8:23

























              answered Dec 21 '13 at 7:58









              slmslm

              255k71541687




              255k71541687












              • 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





                @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











              • @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






              • 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











              • 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













              31














              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.





              share|improve this answer




















              • 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 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






              • 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















              31














              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.





              share|improve this answer




















              • 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 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






              • 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













              31












              31








              31







              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.





              share|improve this answer















              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.






              share|improve this answer














              share|improve this answer



              share|improve this answer








              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 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






              • 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





                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 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






              • 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











              7














              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.






              share|improve this answer























              • 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















              7














              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.






              share|improve this answer























              • 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













              7












              7








              7







              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.






              share|improve this answer













              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.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              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

















              • 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











              4














              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.






              share|improve this answer























              • 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















              4














              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.






              share|improve this answer























              • 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













              4












              4








              4







              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.






              share|improve this answer













              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.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              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

















              • 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











              2














              /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)





              share|improve this answer























              • 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, 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











              • @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















              2














              /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)





              share|improve this answer























              • 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, 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











              • @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













              2












              2








              2







              /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)





              share|improve this answer













              /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)






              share|improve this answer












              share|improve this answer



              share|improve this answer










              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, 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











              • @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







              • 1





                @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











              • @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











              2














              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






              share|improve this answer



























                2














                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






                share|improve this answer

























                  2












                  2








                  2







                  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






                  share|improve this answer













                  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







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 5 '16 at 15:36









                  efesaidefesaid

                  1772




                  1772





















                      2














                      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/






                      share|improve this answer



























                        2














                        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/






                        share|improve this answer

























                          2












                          2








                          2







                          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/






                          share|improve this answer













                          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/







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Sep 1 '16 at 20:29









                          VanuanVanuan

                          1213




                          1213





















                              0














                              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.






                              share|improve this answer



























                                0














                                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.






                                share|improve this answer

























                                  0












                                  0








                                  0







                                  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.






                                  share|improve this answer













                                  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.







                                  share|improve this answer












                                  share|improve this answer



                                  share|improve this answer










                                  answered Aug 9 '16 at 7:55









                                  AlexAlex

                                  4021515




                                  4021515





















                                      0














                                      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.






                                      share|improve this answer



























                                        0














                                        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.






                                        share|improve this answer

























                                          0












                                          0








                                          0







                                          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.






                                          share|improve this answer













                                          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.







                                          share|improve this answer












                                          share|improve this answer



                                          share|improve this answer










                                          answered Sep 29 '16 at 7:04









                                          mkapturmkaptur

                                          11




                                          11





















                                              0














                                              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.






                                              share|improve this answer

























                                              • see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox

                                                – myrdd
                                                Jun 17 '18 at 11:59















                                              0














                                              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.






                                              share|improve this answer

























                                              • see also unix.stackexchange.com/q/396678/231113 in case you are using proxmox

                                                – myrdd
                                                Jun 17 '18 at 11:59













                                              0












                                              0








                                              0







                                              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.






                                              share|improve this answer















                                              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.







                                              share|improve this answer














                                              share|improve this answer



                                              share|improve this answer








                                              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

















                                              • 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











                                              0














                                              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)






                                              share|improve this answer



























                                                0














                                                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)






                                                share|improve this answer

























                                                  0












                                                  0








                                                  0







                                                  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)






                                                  share|improve this answer













                                                  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)







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Jan 19 '18 at 8:35









                                                  user3737396user3737396

                                                  1




                                                  1





















                                                      0














                                                      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.






                                                      share|improve this answer


















                                                      • 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















                                                      0














                                                      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.






                                                      share|improve this answer


















                                                      • 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













                                                      0












                                                      0








                                                      0







                                                      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.






                                                      share|improve this answer













                                                      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.







                                                      share|improve this answer












                                                      share|improve this answer



                                                      share|improve this answer










                                                      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/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












                                                      • 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







                                                      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











                                                      0














                                                      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)





                                                      share|improve this answer























                                                      • 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















                                                      0














                                                      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)





                                                      share|improve this answer























                                                      • 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













                                                      0












                                                      0








                                                      0







                                                      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)





                                                      share|improve this answer













                                                      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)






                                                      share|improve this answer












                                                      share|improve this answer



                                                      share|improve this answer










                                                      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

















                                                      • 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











                                                      0














                                                      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.






                                                      share|improve this answer



























                                                        0














                                                        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.






                                                        share|improve this answer

























                                                          0












                                                          0








                                                          0







                                                          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.






                                                          share|improve this answer













                                                          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.







                                                          share|improve this answer












                                                          share|improve this answer



                                                          share|improve this answer










                                                          answered 2 days ago









                                                          Dale AndersonDale Anderson

                                                          33128




                                                          33128















                                                              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?



                                                              Popular posts from this blog

                                                              Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

                                                              대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495

                                                              Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition