March 3, 20251 yr Diagnostic attached. Any guidance is greatly appreciated. Thank you, Dustin borg-diagnostics-20250303-1535.zip
March 4, 20251 yr Community Expert First syslog is empty, so cannot see the begging of the issue, but the spam is CIFS related, reboot and post new diags after using the server for a few minutes.
March 4, 20251 yr Author Log only at 5% full ATM. borg-diagnostics-20250304-1433.zip Edited March 4, 20251 yr by Dustin Turner
March 4, 20251 yr Author Diag after a restart and about 5 minutes. borg-diagnostics-20250304-1444.zip
March 5, 20251 yr Community Expert There's no more info in the log, the issues starts from here: Mar 4 21:44:51 Borg kernel: CIFS: __readahead_batch() returned 3/16 ### [PREVIOUS LINE REPEATED 296 TIMES] ### So possibly, an issue with some shares that you started using at that time, I would recommend starting by removing the root share hack from SMB extras: [rootshare] path = /mnt/user comment = browseable = yes valid users = donjuan write list = donjuan vfs objects =
March 6, 20251 yr Author Logs full again. Seems to happen overnight. borg-diagnostics-20250306-0811.zip
March 6, 20251 yr Community Expert Your logspace is full, and syslog is getting spammed by those same CIFS entries. But not clear that syslog is taking all that space. What do you get from command line with this? du -h /var/log
March 6, 20251 yr Author 0 /var/log/pwfail 0 /var/log/swtpm/libvirt/qemu 0 /var/log/swtpm/libvirt 0 /var/log/swtpm 0 /var/log/samba/cores/rpcd_winreg 0 /var/log/samba/cores/rpcd_classic 0 /var/log/samba/cores/rpcd_lsad 0 /var/log/samba/cores/samba-dcerpcd 0 /var/log/samba/cores/winbindd 0 /var/log/samba/cores/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 8.0K /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools/removed_scripts 0 /var/log/pkgtools/removed_packages 0 /var/log/pkgtools 4.0K /var/log/nginx 0 /var/log/nfsd 0 /var/log/libvirt/qemu 0 /var/log/libvirt/ch 4.0K /var/log/libvirt 176K /var/log
March 6, 20251 yr Are you using NFS anywhere? Shouldn't affect SMB, but disable NFS if you're not utilizing it
March 7, 20251 yr Author Log less than 5% this morning. Such weird behavior. borg-diagnostics-20250307-0813.zip
March 8, 20251 yr Community Expert On 3/6/2025 at 8:17 AM, trurl said: Your logspace is full, and syslog is getting spammed by those same CIFS entries. But not clear that syslog is taking all that space. What do you get from command line with this? du -h /var/log
March 8, 20251 yr Author 0 /var/log/pwfail 0 /var/log/swtpm/libvirt/qemu 0 /var/log/swtpm/libvirt 0 /var/log/swtpm 0 /var/log/samba/cores/rpcd_lsad 0 /var/log/samba/cores/samba-dcerpcd 0 /var/log/samba/cores/winbindd 0 /var/log/samba/cores/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 8.0K /var/log/samba 0 /var/log/plugins 0 /var/log/pkgtools/removed_scripts 0 /var/log/pkgtools/removed_packages 0 /var/log/pkgtools 4.0K /var/log/nginx 0 /var/log/nfsd 0 /var/log/libvirt/qemu 0 /var/log/libvirt/ch 4.0K /var/log/libvirt 128M /var/log root@Borg:~#
March 9, 20251 yr Community Expert It does appear to be just the CIFS messages causing the issue, note that ion the diags doesn't show all the entries: ... ### [PREVIOUS LINE REPEATED 4577 TIMES] ### ... ### [PREVIOUS LINE REPEATED 492 TIMES] ### ... ### [PREVIOUS LINE REPEATED 2763 TIMES] ### ... ### [PREVIOUS LINE REPEATED 1462 TIMES] ###
March 9, 20251 yr Community Expert CIFS is just SMB, but those log entries don't suggest to me where the source of the problem is. One possibility might be //172.16.69.198/TV 97T 84T 13T 88% /mnt/remotes/172.16.69.198_TV Reboot and disconnect that to see if the problem continues.
March 9, 20251 yr Author //172.16.69.198/TV is my Synology NAS that has my Archived TV collection. I can restart it, but disconnecting will be an issue. It may sound like Sonarr is scanning the whole collection at night. I just need to know how to stop the logging on it.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.