So, as you can see it claims that the resource is temporarily unavailable but it appears to be able to access said resource nonetheless. Still, I would like to know what is going on and how I could fix this problem. Any ideas?
Edit: It seem like the -l flag is the culprit, i.e. ls -ash works fine.
I see you are mounting a windows style mount in Linux.
I’m a bit out of my depth on this one because I do not use windows mounts in linux.
For network mount I always recommend using something like NFS or raw block storage.
I’m not sure if it matters or not but for for network drives I always append the _netdev to the file mount options to ensure linux knows it’s a network drive. I am not sure if that is applicable for a SMB share.
Thx and sorry for the late reply. I will investigate if _netdev is available for smb shares. I am using smb because I have both, Windows, Linux and macOS clients and smb is compatible with all of them.
I will update this thread if it solves my problem.