Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "R. Diez" <rdiez-2006@rd10.de>
To: linux-cifs@vger.kernel.org
Subject: Long system-wide pauses when CIFS server unreachable
Date: Mon, 7 Oct 2024 10:26:30 +0200	[thread overview]
Message-ID: <b00ade8a-3cf6-40f9-8015-1602c12ee890@rd10.de> (raw)

Hi all:

Today I forgot again to unmount a CIFS mount before turning my Windows 10 PC off. After resuming my Linux laptop from sleep, the file manager and other applications froze for a number of minutes.

Unmounting the unresponsive mount was difficult. Command "lsof | grep mountpoint" showed nothing. I am using echo_interval=4, but that does not help.

I reported this issue here some months ago, and got some feedback from Lucy Kueny, but otherwise CIFS maintainers were silent:

Subject: How to automatically drop unresponsive CIFS /SMB connections
Date: Sat, 3 Feb 2024 23:48:42 +0100	
https://lore.kernel.org/linux-cifs/428ab7ba-0960-4e5e-a4ab-290dac58f45b@rd10.de/

I have been experiencing this problem for years, both at home and at work, with a variety of Linux and Windows versions. It is a well-known pitfall.

I think that this is actually a serious issue. Most users wouldn't know why the Linux system is suddenly unresponsive, or how to fix it. Even restarting a system with a hanging CIFS connection is problematic.

I am using Ubuntu 22.04.5, kernel version 6.8.0-45-generic.

Is there some new work-around available nowadays? Otherwise, is there any chance that the CIFS maintainers will take this problem seriously?

I am considering switching to OpenSSH for Windows, but I can only do that with my personal Windows computers. NFS for Windows is probably not an option. In a business environment, most Windows sysadmins will not install other network protocols anyway just because Linux has issues, so there is not much most Linux users can do.

Regards,
   rdiez


                 reply	other threads:[~2024-10-07  8:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b00ade8a-3cf6-40f9-8015-1602c12ee890@rd10.de \
    --to=rdiez-2006@rd10.de \
    --cc=linux-cifs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox