Re: NFS server (round-robin IP) times out: How does autofs behave? How can we fix that on the client side?

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

 



On 12/21/18 11:02 AM, Frank Thommen wrote:
Dear all.

@work we are struggling with NFS server timeouts and subsequentially missing mounts on the clients:

[...]
Dec 21 10:12:20 XXX kernel: nfs: server SRV not responding, timed out
Dec 21 10:12:20 XXX automount[41879]: mount(nfs): nfs: mount failure SRV:/a/b/c on /d/e/f
[...]

The server timing out is a storage cluster with multiple IPs, served in round-robin mode.  Does autofs in cases of connectivity problems try to resolve the server name multiple times - and then maybe get a "good" IP - or is it "stuck" on the IP it get's when the initial mount request is made?

If autofs does not re-resolve server names: Is there a way to provide autofs with multiple names/ips which autofs tries all to find a possibly working head node?  How would this have to be configured?

I found the "Replicated Server" feature. How does autofs use the different entries? Does it make a "round-robin" on it's own? And how does autofs behave, if one of the multiple entries is not reachable or the NFS server times out?

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