NFS Share on Centos 7 Fails to automountautomount nfs: autofs timeout settings for unreliable servers - how to avoid hangup?Automount cdrom when accessed via NFSAutomount not equivelent to mount?Not able to automount NFS shareNFS share mounting issueAutoFS fails to mount Samba CIFS shareAutofs Issues Mounting NFS Home Directories (CentOS 7.4)archlinux netboot diskless node/system, systemd on NFS (v4) fails, rpc.idmapdIdle timeout for NFS share mounted with systemd automount

Why do phishing e-mails use faked e-mail addresses instead of the real one?

Ultrafilters as a double dual

Was it really inappropriate to write a pull request for the company I interviewed with?

Interpretation of linear regression interaction term plot

What does it take to become a wilderness skills guide as a business?

Does the US political system, in principle, allow for a no-party system?

Is there a logarithm base for which the logarithm becomes an identity function?

How would an energy-based "projectile" blow up a spaceship?

Boss Telling direct supervisor I snitched

Can I challenge the interviewer to give me a proper technical feedback?

What is Tony Stark injecting into himself in Iron Man 3?

Is divide-by-zero a security vulnerability?

Rationale to prefer local variables over instance variables?

Exempt portion of equation line from aligning?

School performs periodic password audits. Is my password compromised?

How to make sure I'm assertive enough in contact with subordinates?

What should I do when a paper is published similar to my PhD thesis without citation?

direct sum of representation of product groups

If nine coins are tossed, what is the probability that the number of heads is even?

Why is there an extra space when I type "ls" on the Desktop?

How can I portion out frozen cookie dough?

Does an unused member variable take up memory?

Why do we say 'Pairwise Disjoint', rather than 'Disjoint'?

I've given my players a lot of magic items. Is it reasonable for me to give them harder encounters?



NFS Share on Centos 7 Fails to automount


automount nfs: autofs timeout settings for unreliable servers - how to avoid hangup?Automount cdrom when accessed via NFSAutomount not equivelent to mount?Not able to automount NFS shareNFS share mounting issueAutoFS fails to mount Samba CIFS shareAutofs Issues Mounting NFS Home Directories (CentOS 7.4)archlinux netboot diskless node/system, systemd on NFS (v4) fails, rpc.idmapdIdle timeout for NFS share mounted with systemd automount













1















I have a fresh install of Centos 7. I cannot seem to auto mount an NFS share located on 192.168.254.105:/srv/nfsshare from the Centos client.



Mounting the share manually however, works perfectly.



/etc/auto.master has been commented out completely to simplify the problem, save for the following line:



/- /etc/auto.nfsshare 


/etc/auto.nfsshare holds the following line:



/tests/nfsshare -fstype=nfs,credentials=/etc/credentials.txt 192.168.254.105:/srv/nfsshare


/etc/credentials.txt holds:



 user=user
password=password


The expected behavior is that when I ls -l /tests/nfsshare, I will see a few files that my fileserver's /srv/nfsshare directory holds.



It does not. Instead, it shows nothing.



The logs from sudo journalctl --unit=autofs.service shows this when it starts (debug enabled):



 Nov 20 00:25:38 localhost.localdomain systemd[1]: Starting Automounts filesystems on demand...
Nov 20 00:25:38 localhost.localdomain automount[21204]: Starting automounter version 5.0.7-48.el7, master map auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: using kernel protocol version 5.02
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_master: reading master files auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_read_master: lookup(file): read entry /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: master_do_mount: mounting /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: automount_path_to_fifo: fifo name /run/autofs.fifo--
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_map: reading map file /etc/auto.nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: mounted direct on /tests/nfsshare with timeout 300, freq 75 seconds
Nov 20 00:25:38 localhost.localdomain automount[21204]: do_mount_autofs_direct: mounted trigger /tests/nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: st_ready: st_ready(): state = 0 path /-
Nov 20 00:25:38 localhost.localdomain systemd[1]: Started Automounts filesystems on demand.


The following appears in my logs when I attempt to force mounting of the nfs share via ls -l /tests/nfsshare:



 Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 21, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: attempting to mount entry /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): looking up /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): /tests/nfsshare -> -fstype=nfs,credentials=/etc/credenti...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): expanded entry: -fstype=nfs,credentials=/etc/credentials.tx...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): gathered options: fstype=nfs,credentials=/etc/credentials.txt
Nov 20 00:48:05 localhost.localdomain automount[22030]: [90B blob data]
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 21
Nov 20 00:48:05 localhost.localdomain automount[22030]: failed to mount /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 22, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 22


Additionally, ls -l /tests/nfsshare actually produces the error:



 ls: cannot access nfsshare/: No such file or directory


How can I fix this issue? As stated before, manual mounting the share works fine.




EDIT: as requested, output of ls -la /etc/auto.nfsshare



-rw-r--r--. 1 root root 99 Nov 20 00:25 /etc/auto.nfsshare









share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • could you please show us the output of "ls -la /etc/auto.nfsshare"?

    – Rui F Ribeiro
    Nov 19 '15 at 20:54











  • @RuiFRibeiro output appended!

    – steelmonkey
    Nov 19 '15 at 21:03











  • seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

    – Rui F Ribeiro
    Nov 19 '15 at 21:10











  • @RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

    – steelmonkey
    Nov 20 '15 at 2:54











  • What is the version of NFS by default on both sides?

    – Rui F Ribeiro
    Nov 20 '15 at 7:59















1















I have a fresh install of Centos 7. I cannot seem to auto mount an NFS share located on 192.168.254.105:/srv/nfsshare from the Centos client.



Mounting the share manually however, works perfectly.



/etc/auto.master has been commented out completely to simplify the problem, save for the following line:



/- /etc/auto.nfsshare 


/etc/auto.nfsshare holds the following line:



/tests/nfsshare -fstype=nfs,credentials=/etc/credentials.txt 192.168.254.105:/srv/nfsshare


/etc/credentials.txt holds:



 user=user
password=password


The expected behavior is that when I ls -l /tests/nfsshare, I will see a few files that my fileserver's /srv/nfsshare directory holds.



It does not. Instead, it shows nothing.



The logs from sudo journalctl --unit=autofs.service shows this when it starts (debug enabled):



 Nov 20 00:25:38 localhost.localdomain systemd[1]: Starting Automounts filesystems on demand...
Nov 20 00:25:38 localhost.localdomain automount[21204]: Starting automounter version 5.0.7-48.el7, master map auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: using kernel protocol version 5.02
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_master: reading master files auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_read_master: lookup(file): read entry /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: master_do_mount: mounting /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: automount_path_to_fifo: fifo name /run/autofs.fifo--
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_map: reading map file /etc/auto.nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: mounted direct on /tests/nfsshare with timeout 300, freq 75 seconds
Nov 20 00:25:38 localhost.localdomain automount[21204]: do_mount_autofs_direct: mounted trigger /tests/nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: st_ready: st_ready(): state = 0 path /-
Nov 20 00:25:38 localhost.localdomain systemd[1]: Started Automounts filesystems on demand.


The following appears in my logs when I attempt to force mounting of the nfs share via ls -l /tests/nfsshare:



 Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 21, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: attempting to mount entry /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): looking up /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): /tests/nfsshare -> -fstype=nfs,credentials=/etc/credenti...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): expanded entry: -fstype=nfs,credentials=/etc/credentials.tx...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): gathered options: fstype=nfs,credentials=/etc/credentials.txt
Nov 20 00:48:05 localhost.localdomain automount[22030]: [90B blob data]
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 21
Nov 20 00:48:05 localhost.localdomain automount[22030]: failed to mount /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 22, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 22


Additionally, ls -l /tests/nfsshare actually produces the error:



 ls: cannot access nfsshare/: No such file or directory


How can I fix this issue? As stated before, manual mounting the share works fine.




EDIT: as requested, output of ls -la /etc/auto.nfsshare



-rw-r--r--. 1 root root 99 Nov 20 00:25 /etc/auto.nfsshare









share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • could you please show us the output of "ls -la /etc/auto.nfsshare"?

    – Rui F Ribeiro
    Nov 19 '15 at 20:54











  • @RuiFRibeiro output appended!

    – steelmonkey
    Nov 19 '15 at 21:03











  • seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

    – Rui F Ribeiro
    Nov 19 '15 at 21:10











  • @RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

    – steelmonkey
    Nov 20 '15 at 2:54











  • What is the version of NFS by default on both sides?

    – Rui F Ribeiro
    Nov 20 '15 at 7:59













1












1








1








I have a fresh install of Centos 7. I cannot seem to auto mount an NFS share located on 192.168.254.105:/srv/nfsshare from the Centos client.



Mounting the share manually however, works perfectly.



/etc/auto.master has been commented out completely to simplify the problem, save for the following line:



/- /etc/auto.nfsshare 


/etc/auto.nfsshare holds the following line:



/tests/nfsshare -fstype=nfs,credentials=/etc/credentials.txt 192.168.254.105:/srv/nfsshare


/etc/credentials.txt holds:



 user=user
password=password


The expected behavior is that when I ls -l /tests/nfsshare, I will see a few files that my fileserver's /srv/nfsshare directory holds.



It does not. Instead, it shows nothing.



The logs from sudo journalctl --unit=autofs.service shows this when it starts (debug enabled):



 Nov 20 00:25:38 localhost.localdomain systemd[1]: Starting Automounts filesystems on demand...
Nov 20 00:25:38 localhost.localdomain automount[21204]: Starting automounter version 5.0.7-48.el7, master map auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: using kernel protocol version 5.02
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_master: reading master files auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_read_master: lookup(file): read entry /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: master_do_mount: mounting /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: automount_path_to_fifo: fifo name /run/autofs.fifo--
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_map: reading map file /etc/auto.nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: mounted direct on /tests/nfsshare with timeout 300, freq 75 seconds
Nov 20 00:25:38 localhost.localdomain automount[21204]: do_mount_autofs_direct: mounted trigger /tests/nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: st_ready: st_ready(): state = 0 path /-
Nov 20 00:25:38 localhost.localdomain systemd[1]: Started Automounts filesystems on demand.


The following appears in my logs when I attempt to force mounting of the nfs share via ls -l /tests/nfsshare:



 Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 21, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: attempting to mount entry /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): looking up /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): /tests/nfsshare -> -fstype=nfs,credentials=/etc/credenti...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): expanded entry: -fstype=nfs,credentials=/etc/credentials.tx...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): gathered options: fstype=nfs,credentials=/etc/credentials.txt
Nov 20 00:48:05 localhost.localdomain automount[22030]: [90B blob data]
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 21
Nov 20 00:48:05 localhost.localdomain automount[22030]: failed to mount /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 22, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 22


Additionally, ls -l /tests/nfsshare actually produces the error:



 ls: cannot access nfsshare/: No such file or directory


How can I fix this issue? As stated before, manual mounting the share works fine.




EDIT: as requested, output of ls -la /etc/auto.nfsshare



-rw-r--r--. 1 root root 99 Nov 20 00:25 /etc/auto.nfsshare









share|improve this question
















I have a fresh install of Centos 7. I cannot seem to auto mount an NFS share located on 192.168.254.105:/srv/nfsshare from the Centos client.



Mounting the share manually however, works perfectly.



/etc/auto.master has been commented out completely to simplify the problem, save for the following line:



/- /etc/auto.nfsshare 


/etc/auto.nfsshare holds the following line:



/tests/nfsshare -fstype=nfs,credentials=/etc/credentials.txt 192.168.254.105:/srv/nfsshare


/etc/credentials.txt holds:



 user=user
password=password


The expected behavior is that when I ls -l /tests/nfsshare, I will see a few files that my fileserver's /srv/nfsshare directory holds.



It does not. Instead, it shows nothing.



The logs from sudo journalctl --unit=autofs.service shows this when it starts (debug enabled):



 Nov 20 00:25:38 localhost.localdomain systemd[1]: Starting Automounts filesystems on demand...
Nov 20 00:25:38 localhost.localdomain automount[21204]: Starting automounter version 5.0.7-48.el7, master map auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: using kernel protocol version 5.02
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_master: reading master files auto.master
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_read_master: lookup(file): read entry /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: master_do_mount: mounting /-
Nov 20 00:25:38 localhost.localdomain automount[21204]: automount_path_to_fifo: fifo name /run/autofs.fifo--
Nov 20 00:25:38 localhost.localdomain automount[21204]: lookup_nss_read_map: reading map file /etc/auto.nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: parse_init: parse(sun): init gathered global options: (null)
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_mount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: spawn_umount: mtab link detected, passing -n to mount
Nov 20 00:25:38 localhost.localdomain automount[21204]: mounted direct on /tests/nfsshare with timeout 300, freq 75 seconds
Nov 20 00:25:38 localhost.localdomain automount[21204]: do_mount_autofs_direct: mounted trigger /tests/nfsshare
Nov 20 00:25:38 localhost.localdomain automount[21204]: st_ready: st_ready(): state = 0 path /-
Nov 20 00:25:38 localhost.localdomain systemd[1]: Started Automounts filesystems on demand.


The following appears in my logs when I attempt to force mounting of the nfs share via ls -l /tests/nfsshare:



 Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 21, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: attempting to mount entry /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): looking up /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: lookup_mount: lookup(file): /tests/nfsshare -> -fstype=nfs,credentials=/etc/credenti...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): expanded entry: -fstype=nfs,credentials=/etc/credentials.tx...fsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: parse_mount: parse(sun): gathered options: fstype=nfs,credentials=/etc/credentials.txt
Nov 20 00:48:05 localhost.localdomain automount[22030]: [90B blob data]
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 21
Nov 20 00:48:05 localhost.localdomain automount[22030]: failed to mount /tests/nfsshare
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet: type = 5
Nov 20 00:48:05 localhost.localdomain automount[22030]: handle_packet_missing_direct: token 22, name /tests/nfsshare, request pid 22057
Nov 20 00:48:05 localhost.localdomain automount[22030]: dev_ioctl_send_fail: token = 22


Additionally, ls -l /tests/nfsshare actually produces the error:



 ls: cannot access nfsshare/: No such file or directory


How can I fix this issue? As stated before, manual mounting the share works fine.




EDIT: as requested, output of ls -la /etc/auto.nfsshare



-rw-r--r--. 1 root root 99 Nov 20 00:25 /etc/auto.nfsshare






centos nfs automounting autofs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 19 '15 at 21:02







steelmonkey

















asked Nov 19 '15 at 20:49









steelmonkeysteelmonkey

236




236





bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.














  • could you please show us the output of "ls -la /etc/auto.nfsshare"?

    – Rui F Ribeiro
    Nov 19 '15 at 20:54











  • @RuiFRibeiro output appended!

    – steelmonkey
    Nov 19 '15 at 21:03











  • seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

    – Rui F Ribeiro
    Nov 19 '15 at 21:10











  • @RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

    – steelmonkey
    Nov 20 '15 at 2:54











  • What is the version of NFS by default on both sides?

    – Rui F Ribeiro
    Nov 20 '15 at 7:59

















  • could you please show us the output of "ls -la /etc/auto.nfsshare"?

    – Rui F Ribeiro
    Nov 19 '15 at 20:54











  • @RuiFRibeiro output appended!

    – steelmonkey
    Nov 19 '15 at 21:03











  • seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

    – Rui F Ribeiro
    Nov 19 '15 at 21:10











  • @RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

    – steelmonkey
    Nov 20 '15 at 2:54











  • What is the version of NFS by default on both sides?

    – Rui F Ribeiro
    Nov 20 '15 at 7:59
















could you please show us the output of "ls -la /etc/auto.nfsshare"?

– Rui F Ribeiro
Nov 19 '15 at 20:54





could you please show us the output of "ls -la /etc/auto.nfsshare"?

– Rui F Ribeiro
Nov 19 '15 at 20:54













@RuiFRibeiro output appended!

– steelmonkey
Nov 19 '15 at 21:03





@RuiFRibeiro output appended!

– steelmonkey
Nov 19 '15 at 21:03













seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

– Rui F Ribeiro
Nov 19 '15 at 21:10





seems ok. How about adding "rpcbind: 192.168.254.105" in /etc/hosts.allow does it solve it?

– Rui F Ribeiro
Nov 19 '15 at 21:10













@RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

– steelmonkey
Nov 20 '15 at 2:54





@RuiFRibeiro added your text to /etc/hosts.allow. set selinux to permissive, stopped firewalld via systemctl. still nothing.

– steelmonkey
Nov 20 '15 at 2:54













What is the version of NFS by default on both sides?

– Rui F Ribeiro
Nov 20 '15 at 7:59





What is the version of NFS by default on both sides?

– Rui F Ribeiro
Nov 20 '15 at 7:59










2 Answers
2






active

oldest

votes


















0














I had the same problem.



Configuration is fine, but directory does not exist, although is seems created.



The solution in my particular case was that the file was an UTF-8 file, which autofs cannot read (that's why you get the Blob message in the logging).



Recreate the file, and make sure it is an ascii file.
After I changed that, everything worked flawlessly.






share|improve this answer






























    0














    I haven't encoutered username/password protected NFS share so far.



    Anyway, you can make good use of systemd features here (example for a basic NFS share you would want to mount in /tests/nfsshare).



    192.168.254.105:/srv/nfsshare /tests/nfsshare nfs users,_netdev,x-systemd.automount 0 0





    share|improve this answer






















      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f244205%2fnfs-share-on-centos-7-fails-to-automount%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      I had the same problem.



      Configuration is fine, but directory does not exist, although is seems created.



      The solution in my particular case was that the file was an UTF-8 file, which autofs cannot read (that's why you get the Blob message in the logging).



      Recreate the file, and make sure it is an ascii file.
      After I changed that, everything worked flawlessly.






      share|improve this answer



























        0














        I had the same problem.



        Configuration is fine, but directory does not exist, although is seems created.



        The solution in my particular case was that the file was an UTF-8 file, which autofs cannot read (that's why you get the Blob message in the logging).



        Recreate the file, and make sure it is an ascii file.
        After I changed that, everything worked flawlessly.






        share|improve this answer

























          0












          0








          0







          I had the same problem.



          Configuration is fine, but directory does not exist, although is seems created.



          The solution in my particular case was that the file was an UTF-8 file, which autofs cannot read (that's why you get the Blob message in the logging).



          Recreate the file, and make sure it is an ascii file.
          After I changed that, everything worked flawlessly.






          share|improve this answer













          I had the same problem.



          Configuration is fine, but directory does not exist, although is seems created.



          The solution in my particular case was that the file was an UTF-8 file, which autofs cannot read (that's why you get the Blob message in the logging).



          Recreate the file, and make sure it is an ascii file.
          After I changed that, everything worked flawlessly.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 16 '16 at 13:58









          RobRob

          1




          1























              0














              I haven't encoutered username/password protected NFS share so far.



              Anyway, you can make good use of systemd features here (example for a basic NFS share you would want to mount in /tests/nfsshare).



              192.168.254.105:/srv/nfsshare /tests/nfsshare nfs users,_netdev,x-systemd.automount 0 0





              share|improve this answer



























                0














                I haven't encoutered username/password protected NFS share so far.



                Anyway, you can make good use of systemd features here (example for a basic NFS share you would want to mount in /tests/nfsshare).



                192.168.254.105:/srv/nfsshare /tests/nfsshare nfs users,_netdev,x-systemd.automount 0 0





                share|improve this answer

























                  0












                  0








                  0







                  I haven't encoutered username/password protected NFS share so far.



                  Anyway, you can make good use of systemd features here (example for a basic NFS share you would want to mount in /tests/nfsshare).



                  192.168.254.105:/srv/nfsshare /tests/nfsshare nfs users,_netdev,x-systemd.automount 0 0





                  share|improve this answer













                  I haven't encoutered username/password protected NFS share so far.



                  Anyway, you can make good use of systemd features here (example for a basic NFS share you would want to mount in /tests/nfsshare).



                  192.168.254.105:/srv/nfsshare /tests/nfsshare nfs users,_netdev,x-systemd.automount 0 0






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Feb 4 at 10:46









                  Pierre-Alain TORETPierre-Alain TORET

                  40628




                  40628



























                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f244205%2fnfs-share-on-centos-7-fails-to-automount%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Frič See also Navigation menuinternal link

                      Identify plant with long narrow paired leaves and reddish stems Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?What is this plant with long sharp leaves? Is it a weed?What is this 3ft high, stalky plant, with mid sized narrow leaves?What is this young shrub with opposite ovate, crenate leaves and reddish stems?What is this plant with large broad serrated leaves?Identify this upright branching weed with long leaves and reddish stemsPlease help me identify this bulbous plant with long, broad leaves and white flowersWhat is this small annual with narrow gray/green leaves and rust colored daisy-type flowers?What is this chilli plant?Does anyone know what type of chilli plant this is?Help identify this plant

                      fontconfig warning: “/etc/fonts/fonts.conf”, line 100: unknown “element blank” The 2019 Stack Overflow Developer Survey Results Are In“tar: unrecognized option --warning” during 'apt-get install'How to fix Fontconfig errorHow do I figure out which font file is chosen for a system generic font alias?Why are some apt-get-installed fonts being ignored by fc-list, xfontsel, etc?Reload settings in /etc/fonts/conf.dTaking 30 seconds longer to boot after upgrade from jessie to stretchHow to match multiple font names with a single <match> element?Adding a custom font to fontconfigRemoving fonts from fontconfig <match> resultsBroken fonts after upgrading Firefox ESR to latest Firefox