smbd error log getting full (beta 6.9.30)

[caplam]

Hello,

since i've moved to beta 6.9.30 (was on 6.8.3 before) my log is getting full with that message:

 

Oct 10 05:18:19 godzilla smbd[30856]: [2020/10/10 05:18:19.035061,  0] ../../source3/smbd/dfree.c:140(sys_disk_free)
Oct 10 05:18:19 godzilla smbd[30856]:   sys_disk_free: VFS disk_free failed. Error was : Not a directory

Do you have any idea why i have this error?

godzilla-diagnostics-20201014-1733.zip

[JorgeB]

Samba is more chatty with -beta30, and don't know exactly what that error means but it appears to be related to the enhanced macOS interoperability, do you have that enable? If yes and it's not needed try disabling it.

[caplam]

thank you. It seems it did the trick. And i don't use anymore a macos machine.

Can i just delete syslog.1 syslog.2 and samba/log.smbd.old ?

I have not seen any other method than rebooting to clear logs. It's a bit a pain in the a..

 

[JorgeB]

8 minutes ago, caplam said:

Can i just delete syslog.1 syslog.2 and samba/log.smbd.old ?

Never tried but should be OK.

[caplam]

it's now ok. Deleting the files is ok and syslog is now accessible again.

So no need to reboot.

Perhaps i'll try to browse my unraid server files with a macos machine to see if it's morking normally.

[jungle]

On 10/14/2020 at 11:54 AM, JorgeB said:

Samba is more chatty with -beta30, and don't know exactly what that error means but it appears to be related to the enhanced macOS interoperability, do you have that enable? If yes and it's not needed try disabling it.

Where is this setting located? I think I'm in the same boat...

 

*** EDIT *** sorry I found it, should've looked harder. I use my Share as a back up Share for Time Machine. I would assume I should not then turn this off?

Edited December 16, 2020 by jungle