Carlos E. R. wrote:
On 2013-10-11 12:21, Dave Howorth wrote:
No, the client will sit there until the server comes back next day. That is how it is designed. And certainly the client hasn't crashed at that point. So have you had a crash or not?
The nfs was mounted as /data/external/. The entire /data directory was unaccessible, any process trying hung. Mind, not accessing /data/external/, but /data/. Several processes got stuck, things failed. The machine had to be rebooted to be usable again. mount/umount hung, impossible to remove the nfs mount.
Something weird was happening there. If it's a reproducible, ongoing problem, we can try to solve it, but otherwise trying to draw any conclusions from the circumstances is very error-prone.
Both server and client were setup by yast, so any misconfiguration was due to yast.
I did have a server go down yesterday and after it came back there were odd symptoms when starting new processes on the clients until I went into YaST and restarted the NFS server component. But existing processes weren't affected at all. I don't understand what happened there, and I probably never will.
I'm not sure what behaviour you want your particular client to have. But the most obvious change would be to configure the mount with the soft option. Then your client would have to be aware of possible errors (as it should be in any case of course). When the server goes down, the client will receive an error and it's up to the client to deal with that.
Both are 12.3 machines. So you say Linux is buggy... :-p
Sorry, I don't understand that logic, or how your statement relates to what I said. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org