• Sparsely allocated files are expanded to full size when using mover (cache -> array). (6.5.2-rc2)


    MrChunky
    • Minor

    I am running into an issue where a sparse file is created in cache share by docker. The file is then moved from cache share to the array using mover. On this a full size file is written to the array rather then only the data used.

     

    There is nothing extraordinary in the logs. Just says that the particular file is being moved and the array drive starts writing to itself until the sparse file is fully expanded.

     

    I am on 6.5.2-rc2

     

     




    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.