On Friday 18 October 2024 14:41:03 BST Peter Humphrey wrote: > Greetings, > > Let me try this again. > > Why should an NFS server wait 15 seconds before reporting "No such file or > directory"?
I couldn't find anything conspicuously wrong in your setup, but I don't have much in depth experience working with NFS. A 15 second delay seems excessive to me. Even with resource constrained servers and powered down disks I don't see more than 5 seconds delay here. Whenever I had an error like yours, I traced it down to some typo, gratuitous use of space in the syntax, or some omission in my /etc/exports file. As I was reading your post I thought you could have missed using 'mount --bind' for your /mnt/nfs/portage to /var/ on i5, but you posted you are able to list your portage tree files within it. So this is not the cause of the problem. Differences I noticed compared to my typical setup are: 1. I define a subnet, in addition to the single client's IP address - e.g. 192.168.178.7/255.255.255.254. 2. I do not use 'nohide'. In your case you mount each directory explicitly and they are probably both on the same partition/fs(?), so what purpose does nohide serve? 3. Will all requests come from sub-1024 port numbers, or will some strict/ obscure firewalling cause problems since you specify 'secure'? Some domestic routers try to be too clever by half in this respect. Try setting your exports with 'insecure' to see if it makes any difference. Whenever you change any settings in your exports file remember to run: exportfs -rav You could try tweaking the above options in case it makes a difference. However, if the *same* settings worked with a previous client, then I can't logically explain why they fail now. :-/
signature.asc
Description: This is a digitally signed message part.
