Hot answers tagged nfs
I'm not going to answer your question directly. NFS clients are not guaranteed to see updates very fast. Yes, you can tune parameters to control the delay but the result will be worse caching (and therefore terrible performance) on the clients. Usually when I find myself needing NFS clients to see changes faster I take a step back and ask, "ok, what am I ...
This is called nfs re-export and disallowed by modern linux kernels/distributions. As workaround, try port forwarding on the host M: iptables -t nat -A PREROUTING -p tcp --dport 2049 -j DNAT --to-destination 10.10.10.10:2049 iptables -t nat -A POSTROUTING -p tcp --dport 2049 -j MASQUERADE Do the same for mountd as well, but better to fix mountd port ...
The overlay fs provides a possibility to mount one filesystem on top of other one. You can use your nfs mount as lower fs and some local directory as upper fs. The local change will not be sent to the NFS server. More info: https://git.kernel.org/cgit/linux/kernel/git/mszeredi/vfs.git/tree/Documentation/filesystems/overlayfs.txt?h=overlayfs.current
Dropping the caches shouldn't take much time at all. Are you sure it's really not returning from that echo command for several hours? It makes sense that the machine is slower after the caches are dropped, since files that it could previously read from cache now have to be read from disk.
Red Hat Enterprise Linux defaults to using TCP to transport NFS. TCP is the default transport protocol for NFS version 2 and 3 under Red Hat Enterprise Linux. UDP can be used for compatibility purposes as needed, but is not recommended for wide usage. NFSv4 requires TCP.
Looking at top output is completely wrong. It's about the IOPS. To get a view on the NFS statistics, use nfsstat: Server rpc stats: calls badcalls badauth badclnt xdrcall 40833255 0 0 0 0 Server nfs v3: null getattr setattr lookup access readlink 0 0% 1411374 3% ...
"Timeouts on the browser" in my opinion do not really prove that the NFS is the cause of the problem. You didn't explained your debugging process in enough detail. Try to access the files (you are requesting from the browser) directly from the NFS clients command line. In this kind of situation I would be more suspicious of nginx misconfiguration or some ...
This problem was occurring because I was mounting multiple NFS shares from the same server, not all of which had the same context. As per the RedHat documentation on multiple NFS mounts, I needed to add nosharecache to my fstab line for the mounts. The correct SELinux context is then applied on a mount-by-mount basis. The working line in my fstab is as ...
Only top voted, non community-wiki answers of a minimum length are eligible