Long delay in resuming when a a cifs share is mounted

DoctorDan · 2023-04-02 17:17:40

Hello,
I'm using arch, because it starts with nothing, in an attempt to isolate a resume problem.

At this point my arch only has the bare minimum of packages installed. Basically just enough to install stuff and repair grub. In addition I have installed pm-utils and cifs-utils.

The windows share mounts as expected and can be accessed with no trouble.

If I suspend arch using pm-suspend when the share is mounted, the resume requires ~ 2-1/3 minutes before the command prompt returns. any command that I enter, such as df, generates its output after the 2-1/2 minutes have passed.

If I unmount the share and suspend, the resume takes about 3 seconds before the prompt returns and will accept commands.

DMESG output (last line):
[nnn.nnnnnn] CIFS: VFS: \\192.168.1.200 has not responded in 100 seconds. Reconnecting...

For comparison, if a windows client that has the same share mounted when it suspends, the reconnection is instantaneous, so it does not really seem to be an issue with the server not responding.

I suspect that the "has not responded" message is simply a poor choice of words to describe some delay on the arch side. But what can it be?

It would be really helpful if anyone could explain why this happens and what to do to fix it.

Thank you

seth · 2023-04-02 18:08:31

network?
Why is the CIFS (implicitly) contacted anyway?
What mount options do you use?

a windows client that has the same share mounted when it suspends

Windows doesn't "mount" filesystems in this sense. NTFS has a somewhat similar capacity, but that's neither relevant not comparable.

DoctorDan · 2023-04-02 18:38:09

Why is the CIFS (implicitly) contacted anyway?
Is there some other way?

mount -t cifs //192.168.1.200/Drive_E /mnt/server-e -o credentials=/root .smbcredentials_server,nounix,dir_mode=0777,file_mode=0777

Of course windows doesn't "mount" in the same way as linux. The point is that when windows resumes the server responds immediately so the delay I'm seeing in arch is not because the server is slow to respond.

Thanks

seth · 2023-04-02 18:48:46

https://wiki.archlinux.org/title/Samba#Client
But also try "noauto,x-systemd.automount,x-systemd.device-timeout=10,noatime"

when windows resumes the server responds immediately

Does it? Do you "instantaneously" after the resume contact the share?

Arch Linux

#1 2023-04-02 17:17:40

Long delay in resuming when a a cifs share is mounted

#2 2023-04-02 18:08:31

Re: Long delay in resuming when a a cifs share is mounted

#3 2023-04-02 18:38:09

Re: Long delay in resuming when a a cifs share is mounted

#4 2023-04-02 18:48:46

Re: Long delay in resuming when a a cifs share is mounted

Board footer