• Changing cache slots number during a member removal can result in an unmountable pool

    JorgeB

    By JorgeB

      • Minor

    Don't know if this is a bug or a limitation, but even if it's not a bug maybe something can be done to make it better, this happened to a user recently in this thread and I was able to reproduce it.

     

    How to reproduce:

    -start with a 3 device cache pool

    -unassign cache1

    -re-arrange pool, e.g., re-assign cache3 to cache1 slot, up to here all is working fine

    -change cache slots to 2, now Unraid will indicate cache1 is new and result in an unmountable and damaged cache pool if user starts the array

     

    The procedure works as expected if cache slots aren't changed at the same time, i.e., remove one device from a 3 device pool, re-arrange the devices, start the array to balance the pool down to two devices, stop the array and now you can safely change the number of cache slots, but possibly this can be improved, or maybe make it impossible to change the number of slots when removing (or re-arraging) cache devices or it will likely happen to someone else in the future and result in data loss.

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    bonienl

    Made an update whereby cache slots selection will become disabled when cache devices are re-arranged.

    Available in next release.

     

    • Like 1
    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.