Hello, I'm using network storage for voicemail recording, which works pretty well on responsive servers. However in case of server crash on malfunction even open syscall takes ages to return error, which is just unfortunate. Situation was described in thread "Timeout waaay too long" http://lists.samba.org/archive/linux-cifs-client/2006-February/001203.html and now, afer more than four years, it is not any better. My very problem could be probably solved in userspace with "guard" thread killing stuck open or write syscall and moving to next storage available, but I found such a solution unly. There is interesting notion in post "[PATCH] cifs: hard mount option behaviour" http://lists.samba.org/archive/linux-cifs-client/2010-June/006291.html about what is considered a responsive server today. For now I modified timeouts in SendReceive(2), which improved situation for me, but the real qustion is, how should widely acceptable solution look like. Thanks for your suggestions, ladis -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
