Jump to content

  • Mover is not respecting hardlinks (Same Share)

    danlee

    By danlee

      • Minor

    I have a cache drive (/mnt/user/cache_data) and a share (/mnt/user/data). When mover is initiated, it copies the hard links on the cache as new files to the array, creating two copies of the files. I only noticed it was doing this as I have a plugin on qbittorrent that scans torrents for noHL. I have to continually relink the files by doing a manual scan in sonarr/radarr.

     

    Is anyone else having this issue?

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    shEiD

    Did you find the reason/solution for your problem?
     

    I am doing exactly the same thing as you, without any problems. Mover always handles/recreates hardlinks as it's supposed to. I'm also using a script to keep an eye on files with no hardlinks, so I'm sure mover is working a ok.
    But I would be interested to know, what happened in your case for the mover to "bork" the hardlinks.

    Link to comment
    vtmikel

    Did you solve this?  I’m running the same setup and mover is sometimes not respecting hard links.  Other times it is.

    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...