• [6.9.0 Beta 29] Process smbd using 100% of a single core when accessing or copying data to or form a share


    SelfSD
    • Solved Minor

    I've upgraded from 6.8.3 to try to squash some other bugs my system had and so far beta 29 seems to have solved the problems I had, but with it another problem has come up.

     

    Whenever I'm trying to access a share or copy data to and from a share, /usr/sbin/smbd -D is using 100% of a single core, slowing down file transfers to a crawl, around 20 megabytes per second.

    If I attempt to open another explorer window and browse to a share, any ongoing file transfers completely stop and it takes over a minute to open the share.

     

    This issue seems to affect a single computer at a time. If my desktop is having slowdown issues, my laptop can open and copy files without issues but it experiences the same problems the moment a file transfer starts up.

     

    Diagnosis taken during a single file transfer from the array to my desktop.

    unraid-diagnostics-20201005-1148.zip




    User Feedback

    Recommended Comments

    Upgraded to beta 30 and the problem has not appeared again yet, even after hammering the shares hard. If the SMBD process stays good for another day or two I will close the issue.

    • Like 1
    Link to comment

    Everything is still running smoothly! I feel confident that beta 30 fixed what ever happened to my server in beta 29.

    Link to comment


    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.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.