SAMBA/CIFS
Note: I noticed today that I get a high amount of traffic to this link I had posted to a guide pre disaster event where I had a total loss of my server. I feel guilt that you guys are searching issue related topics I documented the solution for in the past. As a direct result I am working on documenting this issue for us all once more. (It is not in any of my local data or notes, nor in wayback archive :< )
TheI onlyfound waysolutions for this issue involving either kernel patching or changing the cifs settings. I recommend the latter currently as it will cause the least issues. However downgrading the cifs protocol used could finddegrade tosecurity perhaps vs version 3. I am unsure. Do research further if this will be a concern.
Kernel Patching (not currently recommended):
Warning: using this solution broke nvidia-smi in a host with most of its workload being GPU accelerated docker/docker-compose. Updating the kernel may cause other issues but it did resolve this issue without changing the cifs settings and after research led by how I rememberedam solvingcertain this issue I found the only solution is to update the kernel to one which does not have the broken behavior. The following kernel upgrade silenced this issue once and for all on my system, this may be a deviation from your release/distro so its up to you, but it will solvethat the issue oncan mybe systemresolved itwith dida breakkernel GPU passthru :(patch but I knowdon't ultimately a kernel issue isremember what method I didused in the past:previously.
apt-get install linux-generic-hwe-22.04
You should honestly replaceReplace the (22.04) with your distro. But I do not anticipate you should be here if you are not running a version prior to 24.04. My testing is with Ubuntu 22.04.
CIFS Settings (Recommended):
Without changing the kernel patch I seefound thisyou can also get rid of the issue stillby onadding the ,vers=2.1 option in the fstab mount or docker-compose cifs mount.
```
volumes:
plex_config:
driver: local
driver_opts:
type: cifs
o: "iocharset=utf8,username=<username>,password=<somepass>,vers=2.1,rw,uid=<changethistotheproperuid>,file_mode=0777,dir_mode=0777"
device: "//172.22.04150.101/plex_config"
```
If you figurediscover thisa outmore (whatviable kernels/patches cause least issues)solution please feel free to reach out by any method available toand helpI anyonewill who stumbles uponupdate this :Dinformation.