Changes in indirect multi-maps don't become effective w/o autofs restart

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear all,

the autofs manpages says:

"If an indirect map is modified then the change will become effective immediately. If an indirect map uses the browse option, the master map contains direct mount maps or the auto.master map is modified then the autofs service control reload action must be rerun to activate the changes."

However this doesn't seem true when using multi-maps:

In /etc/auto.master:

    /base/data /etc/auto.data


In /etc/auto.data:

   # section 1
   #
   p1  -fstype=nfs,vers=3,sec=sys  srv:/export/p1
   p2  -fstype=nfs,vers=3,sec=sys  srv:/export/p2

   # section 2
   #
   others   -fstype=nfs,vers=3,sec=sys \
      /p3   srv:/export/p2 \
      /p4   srv:/export/p4

When adding an entry

   p5  -fstype=nfs,vers=3,sec=sys  srv:/export/p5

in section 1, I can immediately change into /base/data/p2 and it is mounted. All well. But when I add an entry

   /p5 srv:/export/p5

to section 2, then this new entry is not accessible as /base/data/others/p5 even after a `systemctl reload autofs`. autofs has to be completely restarted. Unfortunately we've had many issues (crashes) with clusterjobs accessing NFS shares during autofs restarts. That's why we'd like to avoid complete autofs restart whenever possible.

Can you confirm that multi-maps are not updated by autofs reloads and/or is there a way to achieve this?


We are running autofs-5.0.7-70.el7_4.1.x86_64 on CentOS 7.4.1708 and we cannot update to newer CentOS releases due to other restrictions (special hardware/drivers).


Cheers
frank





[Index of Archives]     [Linux Filesystem Development]     [Linux Ext4]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux