3 ms·
not sure what you mean exactly, but one thing that has caused tons of trouble here, with sometimes the sole solution being a restart (ok our IT maintainer might
by stinos 13y ago
not sure what you mean exactly, but one thing that has caused tons of trouble here, with sometimes the sole solution being a restart (ok our IT maintainer might be doing something worng, yet..) is the opposite: take a bunch of workstations and a bunch of servers, put home directories and data on servers then put everything together using NFS shares. Run analysis and whatnot on the data. Then make the server go down somehow and watch all workstation getting completely locked up without seemingly ever generating some kind of timeout error instead waiting endlessly on a dead connection.
- rwg 13y agoThat's kinda how NFS was designed to work. NFS comes from the dark ages of networking, where transient network errors were very common, even on local networks. "man nfs" and "man mount.nfs" and search for "soft", "intr", "tcp", and "timeo". It sounds like the solution to your problem is some combination of those options.
- stinos 13y agothanks, will put some more effort into it if it ever happens again
- phaemon 13y agoCheck that you've assigned an FSID to each share in /etc/exports