• I've receive an email this morning


    Code
    /etc/cron.daily/openmediavault-cron-apt:
    cat: write error: No space left on device
    cat: write error: No space left on device
    cat: write error: No space left on device


    So as it seems my /var/log is full


    root@pozz:~# df -h


    root@pozz:~# ls -lahS /var/log | head -20



    daemon.log and debug are huge



    Should I



  • Latest entries from my spammed daemon.log




    I see nmbd is the spammer, my samba logs were set to debug, I set to normal.

    Also I have these settings in the SAMBA


    min receivefile size = 16384

    write cache size = 524288

    getwd cache = yes

    socket options = TCP_NODELAY IPTOS_LOWDELAY

    read raw = yes

    write raw = yes


    Maybe these are the culprits?


    Also should I change settings in rogrotate?


    root@pozz:~# cat /etc/logrotate.conf

  • I deleted the log files (daemon.log and debug) but again daemon.log is growing extremely fast.

    Can you please advise a solution?





  • What kind of logging have you set on the Samba configuration page? These entries come from it.
    Set it to "None" or "Minimum"


    Also note that socket options = TCP_NODELAY IPTOS_LOWDELAY is redundant, as is already applied by default with OMV.

    OMV BUILD - MY NAS KILLER - OMV 6.x + omvextrasorg (updated automatically every week)

    NAS Specs: Core i3-8300 - ASRock H370M-ITX/ac - 8GB RAM - Sandisk Ultra Flair 32GB (OMV), 256GB NVME SSD (Docker Apps), Several HDDs (Data) w/ SnapRAID - Fractal Design Node 304 - Be quiet! Pure Power 11 350W


    My all-in-one SnapRAID script!

  • Thanks I put logging to minimum, it seems the logs are now under control.

    I also deleted all the extra options and now SMB saturate my 1gb lan speed consistently.


    I will monitor the logs and post back if they re being spammed again in a few days.

  • Thanks I put logging to minimum, it seems the logs are now under control.

    I also deleted all the extra options and now SMB saturate my 1gb lan speed consistently.


    I will monitor the logs and post back if they re being spammed again in a few days.

    I'm glad logging is now ok.

    To be honest I just found out that SOME extra features are actually useful.


    Most guides you'll find on the web are outdated or specify redundant values.


    However, these values appear to be still useful.


    Code
    read raw = yes
    write raw = yes
    getwd cache = yes

    OMV BUILD - MY NAS KILLER - OMV 6.x + omvextrasorg (updated automatically every week)

    NAS Specs: Core i3-8300 - ASRock H370M-ITX/ac - 8GB RAM - Sandisk Ultra Flair 32GB (OMV), 256GB NVME SSD (Docker Apps), Several HDDs (Data) w/ SnapRAID - Fractal Design Node 304 - Be quiet! Pure Power 11 350W


    My all-in-one SnapRAID script!

  • You may also like the following:


    Code
    mangled names = no
    # fixes weird file names that cannot be shown by Windows clients
    access based share enum = yes
    # only show shares that are available to user during enumeration
    hide unreadable = yes
    # only shows shares that are available to user during normal use

    OMV BUILD - MY NAS KILLER - OMV 6.x + omvextrasorg (updated automatically every week)

    NAS Specs: Core i3-8300 - ASRock H370M-ITX/ac - 8GB RAM - Sandisk Ultra Flair 32GB (OMV), 256GB NVME SSD (Docker Apps), Several HDDs (Data) w/ SnapRAID - Fractal Design Node 304 - Be quiet! Pure Power 11 350W


    My all-in-one SnapRAID script!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!