Hello rdiez, > Many thanks for confirming that this problem exists and bugs other people too. > Let's hope that the CIFS guys take this problem seriously. The Linux desktop freezing for many seconds in a row is probably putting off many users. On my desktop, the UI can freeze for hours and require a reboot from TTY. The 'recent files' submenu in software seems to trigger repeated connection attempts. This is a major usability issue, and probably why FUSE is used by KDE. > The first issue is that there appears to be no documentation about the Linux Kernel CIFS client's behaviour on connection timeout. I find this frustrating. I have done some research in the past, search for 'echo_interval' here: > Based on my empirical research, there is a fixed 10-second timeout when reconnecting. Therefore, I would rather have an error returned as soon as the connection has been marked as lost by means of 'echo_interval', instead of after attempting to reconnect. > This may be hard to achieve if the reconnection only happens single threaded and on demand (when a process is trying to access a file under the mount point), instead of automatically on the background. As I understand it, the connection is managed in a separate thread. The 10-second timeout depends on multiple smaller timeouts in different parts of the kernel. It's almost impossible to change. I believe the echo_interval triggers will cause a reconnect attempt to happen, thus "freezes" will be gone after echo_interval+10 seconds. It's not the best, but it allows the use of a permanent mount to a NAS without trashing userspace if the network goes out of range. Best regards, Lucy Kueny
