Dear all,
As of late, I experience the following issues with regard to my following Samba setup: I am running a Debian 12 Bookworm instance on my desktop in conjunction with a Debian 11 Bullseye instance on my server. Both boxes are up-to-date regarding maintenance updates.
When mounting my Samba share on my desktop via Nautilus --> Other locations --> Connect to server --> "smb://server/share", I can perform the following file operations without difficulties within Nautlius:
1. copying files from a desktop folder to the Samba share
2. copying files from the Samba share to a desktop folder
3. copying files within the Samba share
However, problems emerge when instead mounting the Samba share via /etc/fstab:
//server/share/home/user/sharecifscredentials=/home/user/.cifs-credentials,uid=1000,gid=10001
Suddenly, copying files within the Samba share (see #3 above) stalls at the beginning of the first file: Though created, no content is being copied. Nautilus indicates that open and active operations exist. When performing the same operation on the command line, the cp command is terminated with the error message "Killed". In such a situation, /proc/fs/cifs/open_files on the desktop exhibits according entries. The desktop shut down procedure would run into a timeout. To prevent this from happening, the Samba share has first to be unmounted via: umount --force --lazy /home/user/share
Most interestingly, file operations from or to local folders remain possible (see #1 and #2 above).
I am a bit puzzled about the sudden emergence of this error on an otherwise stable configuration: My samba configuration has not changed for *ages*. My overall server configuration has not been touched for at least a month. The only reason I can think of are the above maintenance updates executed on a regular basis on both the desktop and the server (and that I might not have paid enough attention to lately).
And I am a bit puzzled about the next steps that I could take to tackle this issue. Has anybody experienced the same or similar issues lately? Or could somebody at least point me into the right direction for solving this issue? I will gladly share more information but am a bit clueless about where to start.
Thanks in advance!
As of late, I experience the following issues with regard to my following Samba setup: I am running a Debian 12 Bookworm instance on my desktop in conjunction with a Debian 11 Bullseye instance on my server. Both boxes are up-to-date regarding maintenance updates.
When mounting my Samba share on my desktop via Nautilus --> Other locations --> Connect to server --> "smb://server/share", I can perform the following file operations without difficulties within Nautlius:
1. copying files from a desktop folder to the Samba share
2. copying files from the Samba share to a desktop folder
3. copying files within the Samba share
However, problems emerge when instead mounting the Samba share via /etc/fstab:
//server/share/home/user/sharecifscredentials=/home/user/.cifs-credentials,uid=1000,gid=10001
Suddenly, copying files within the Samba share (see #3 above) stalls at the beginning of the first file: Though created, no content is being copied. Nautilus indicates that open and active operations exist. When performing the same operation on the command line, the cp command is terminated with the error message "Killed". In such a situation, /proc/fs/cifs/open_files on the desktop exhibits according entries. The desktop shut down procedure would run into a timeout. To prevent this from happening, the Samba share has first to be unmounted via: umount --force --lazy /home/user/share
Most interestingly, file operations from or to local folders remain possible (see #1 and #2 above).
I am a bit puzzled about the sudden emergence of this error on an otherwise stable configuration: My samba configuration has not changed for *ages*. My overall server configuration has not been touched for at least a month. The only reason I can think of are the above maintenance updates executed on a regular basis on both the desktop and the server (and that I might not have paid enough attention to lately).
And I am a bit puzzled about the next steps that I could take to tackle this issue. Has anybody experienced the same or similar issues lately? Or could somebody at least point me into the right direction for solving this issue? I will gladly share more information but am a bit clueless about where to start.
Thanks in advance!
Statistics: Posted by a_priori — 2024-01-20 08:07 — Replies 3 — Views 111