Jump to content
  • High CPU usage


    Lenny Williford
    • Urgent



    User Feedback

    Recommended Comments

    Shfs seems to be one of the culprits, so using exclusive (or disk) shares whenever possible may help.

    • Like 1
    Link to comment

    There was an issue in the Unassigned Devices plugin that could potentially cause high CPU usage,  You've updated UD, now wait and see if it occurs again.

    Link to comment

    i have had high CPU usage too and if i remeber correctly, the mover never moved anything and ended just after i started it.

    what seemed to resolve the problem was to put the shares into order.

    as i have played with them in the past i had some leftovers to be synced from cache to disk so make sure that the column STORAGE corresponds to what you see in the SIZE

    image.thumb.png.5cfd3228f21769b1edb6a0a3ec696ee8.png

    if it says CACHE you shall see the disk usage only on CACHE.

    if you find discrepancies, move the files through an SSH session from or to the /mnt/user0

    for example if you find this

    image.thumb.png.86f15774451527b3dddfada03820a83a.png

    it shows that DOWNLOADS share belongs to Array but data on Cache is present so you need to move it manually (or delete from cache)

    then run the mover to sync things again

     

    after that my CPU (and IOWAIT) is back to normal

    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.

×
×
  • Create New...