Jump to content
  • 6.12.6 potential file deletion bug by mover

    • Minor

    Hi all,


    I have been experiencing some (what looked like) "random" file deletion in a share.


    Basically, I have a "downloads" share where several dockers leave their download files (whether torrents or otherwise). Had no problem whatsoever before 6.12. This was on a separate cache pool having a unique cache drive. I was moving files manually when and if required.


    Since 6.12.14 (and now .16), I have been having issues with files mysteriously disappearing from that folder. Whenever they were torrent dowload results, I still had a ".fuse_xxxxx" file leftover as the file was still being "in use".


    The "new" download share is not on 1 drive, but on its own separate cache pool of 3 zfs drives (3x1TB nvme as raidz1). that pool was set with Cache as main storage and array as secondary... I was foolishly thinking it wass good as things would thenm silently get transfered to the array on a regular basis.


    It turns out that the mover process, when running, does NOT transfer to the array. It simply DELETES the files. So (to me),, it seems thast there is a bug either in the mover process, or in the way ZFS pools are handled. 


    Could it be they are not considered as "disks" instead of "shares" and we are hitting the old do_not_copy_from_share_to_disk bug? (or something to that effect, I recall there was a situation that could result in data loss).


    In any case, if I disable the second storage media and leave "cache" on its own without storing on the array, files deletion stops.


    Anyone could confirm and/or help so we can narrow down the issue for sure and get that fixed? I am sure that under no circumstances the mover should be in a position to lose data, regardless of the choices of the end user

    User Feedback

    Recommended Comments

    @denishay This is the first time I have heard of this behaviour so it is probably going to need more information to sort out why it is happening to you .

    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.

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