Jump to content

  • Mover hangs on named pipes

    coppit

    By coppit

      • Minor

    Mover stops on this file:

     

    prw-rw---- 1 201 201 0 Feb 12 11:38 /mnt/disk2/appdata/netdata/cache/.netdata_bash_sleep_timer_fifo|

     

    which is a named pipe. The solution is to log into the server, manually delete the pipe, hard reset your server, and rerun mover.

     

    You can kill mover and restart it without rebooting, but this leaves a "move" process that cannot be killed, and which blocks the share from being unmounted during reboot. A hard server reset is the only way to reboot.

     

    I'm on 6.12.8

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    tetrapod

    I'm 6.12.10 and have the same issue. 

     

    Had this several times while moving appdata to the array and then back to the cache while changing the filesystem on the cache. It scared the hell out of me because I do NOT like to make hard resets and I'm not comfortable killing off processes like these.

    So "Minor" is not good enough for me ;-)

     

    Will do my first reboot now after starting to copy data back to the cache. I see the file it stopped on exists both on the cache and array. Maybe because the cache is now ZFS and has COW? There are quite a bit of these pipe files and I hope I don't have to go through the same thing for all of them :-| 

    • Like 1
    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...