• [6.9.0-beta35] Hardlinking between shares not working properly


    Tomr
    • Minor

    I was said it's unintented behavior and to post there.

     

    Not sure if it's a bug or lack of feature, but mover will not move the hardlink if it's on another share, but rather copy the whole thing. It only works if they are on the same share. I suspect it's because mover works on per-share basis, if it is I ask if something can be done about that?

     

    Steps to reproduce:

     

    Two shares, A And B, both's cache set to Yes with the same pool.

     

    touch /mnt/user/A/test.txt

    cd /mnt/user/A

    ln test.txt /mnt/user/B/test.txt

    ls -i | grep test.txt

    14355223812252192 test.txt

     

     

    cd /mnt/user/B

    ls -i | grep test.txt

    14355223812252192 test.txt

     

    So far so good, they point to the same file.

     

    But if I invoke mover now, thing's change. The files point to other inodes, so the file got copied twice, instead of moving the inode and re-linking the files. They are on the same disk, but point to different inodes.



    User Feedback

    Recommended Comments



    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.