Samba Log file is 4.4 Terabytes

[AlexBussiere]

So here is the problem. I have a Volume called Media. For about a year it has been working great. I recently went on a two week honeymoon - came back and now my server is 100% full. Spent a few hours trying to figure out what happened - I have traced the problem to a file in Media/.system/syslog/log/samba4/ called log.nmdb that is 4.4 TB. The day after I left for vacation, the partition size of Media slowly decreased for day until log file consumed all the available free space from my Volume.

My question is how can I delete this file? Will it restore the available space in the Volume?

Any help would be greatly appreciated!!!

Thanks!
Alex

 

[jgreco]

Code:

echo > /mnt/Media/.system/syslog/log/samba4/log.nmbd

should clear it up. Restart the Samba service afterwards.

 

[DrKK]

By "restart Samba service", the way you should do this is to go to Services->CIFS and turn it off, and on.

Also, this doesn't explain why this happened in the first place. A 4.4TB nmbd log file is highly irregular. What's going on there?

 

[jgreco]

By "restart Samba service", the way you should do this is to go to Services->CIFS and turn it off, and on.

Ideally, but rebooting is also fine.

Also, this doesn't explain why this happened in the first place. A 4.4TB nmbd log file is highly irregular. What's going on there?

(...mutters, "Samba n00b"...) Not as irregular as you'd hope, though the config used in FreeNAS is usually pretty decent about not going all stupid-loggy.

 

[anodos]

Ideally, but rebooting is also fine.



(...mutters, "Samba n00b"...) Not as irregular as you'd hope, though the config used in FreeNAS is usually pretty decent about not going all stupid-loggy.

Never underestimate the ability of samba to do something stupid.

 

[jgreco]

Never underestimate the ability of samba to do something stupid.

exactly that.

 

[anodos]

exactly that.

That said, my guess is that DNS is broken causing samba to idiotically spew 'hostname lookup failed' entries in log.nmbd. The OP should either fix DNS or turn off hostname lookups.