• [v6.8.0] shfs at 100% CPU utilization

    rix

    By rix

      • Closed Minor

    Hi, for the past few weeks I have noticed an odd behaviour by my server on UNRAID 6.8.0:

     

    • After a couple of hours of uptime, one sfhs process stays at 100% cpu utilization
    • Network shares become extremely unresponsive after that (unusably unresponsive)
    • Stopping/Starting the Array resolves the high utilization for a few hours, but results in a parity check
    • Disabling folder caching (the plugin) and even uninstalling it does not resolve the issue

    Please help, this eats a lot of power and makes my server unusable as NAS.

     

    This is my current htop:

    sfhs.thumb.PNG.42a1cda1b547eb8ca8d2dbc882b29b3a.PNG

     

    Diagnostics are attached.

    diagnostics-20200110-2225.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    rix

    I have tried for this to reappear with 6.8.1 for a couple of days - hasnt happened since.

     

    Will close for now

    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.