Hi Shyam, On 27. 02. 24 17:17, Shyam Prasad N wrote:
These messages (in theory) should not show up if either multichannel or max_channels are not specified mount options.
That shouldn't be the case here, I checked with the user and he's not doing anything fishy himself (like interfering with the standard mount utilities), and the userspace tools creating the mounts should not be setting any of these options, which I confirmed by asking for his mounts list:
//192.168.1.12/folder on /mnt/data/supervisor/mounts/folder type cifs (rw,relatime,vers=default,cache=strict,username=user,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,file_mode=0755,dir_mode=0755,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1) //192.168.1.12/folder on /mnt/data/supervisor/media/folder type cifs (rw,relatime,vers=default,cache=strict,username=user,uid=0,noforceuid,gid=0,noforcegid,addr=192.168.1.12,file_mode=0755,dir_mode=0755,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=1)
Or am I missing anything here?
The repeating nature of these messages here leads me to also believe that there's something fishy going on here. Either the network health is not good, or that there's some bug at play here.
Maybe, however I'm not able to reproduce the above behavior yet. But there's been so far one more report of this happening, so it's not a single isolated case. I appreciate any advice what to look at further.
Cheers, Jan
