• 6.11.0 rc3 - Non cache shares now on cache


    miccos
    • Closed

    Hi,
    I just updated to 6.11.0 rc4 and on reboot most of my shares that were set to not use cache are now on cache.
    image.thumb.png.0da23be6a42afea308369a20df47063d.png
    Sorry i paniced and rolled back and the diagnostics is for RC3, but the issue is still present in RC3.
    So i am not sure if it was from the upgrade or something else has happened.

    Thanks

    tower-diagnostics-20220829-1129.zip




    User Feedback

    Recommended Comments

    Fixed up the shares using cache all of a sudden and re-run the upgrade to 6.11.0-RC4.
    No hiccups this time.
    Not really sure what happened in the end.
     

    Link to comment
    20 minutes ago, miccos said:

    Not really sure what happened in the end.

    Probably not related to the update. I don't think that updating would automagically move files.

    Link to comment
    5 hours ago, miccos said:

    Fixed up the shares using cache all of a sudden and re-run the upgrade to 6.11.0-RC4.
    No hiccups this time.
    Not really sure what happened in the end.
     

    One way you can get the symptoms you described is mentioned here in the online documentation accessible via the 'Manual' link at the bottom of the GUI.   If this was the problem, though, it would not be as a result of the upgrade.

    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.