• [6.10.0-rc7] single device pool assignement is not saved

    JorgeB

    By JorgeB

      • Solved Minor

    How to reproduce:

     

    -create a new single device pool

    -assign a device

    -start the array

    -icon will remain blue

    imagem.thumb.png.0efcad72129bd6339a6be4a47ecbf1f7.png

     

    -then when the array is stopped you'll get the data will be deleted warning at array start (but it's not)

    imagem.thumb.png.82f2a59500c81b372db70abc4c579fde.png

     

    -restart the array, after or without re-assigning the device and icon will remain blue.

     

     

    Current workarounds:

     

    -change pool slots to 2, then back to 1

    -reboot with the device assigned

    imagem.thumb.png.5f3386843c6483eb9acbdee1ed18a34b.png

     

    Now it's green and saved.

     

    P.S. this is somewhat related to this issue, I though the cache config wasn't being saved because of the extra spaces in the device name but it was this issue, so now that I saved the new config I don't really care that the device name has an extra underscore.

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    limetech

    Thank you for the reproduction details.  Fixed in next release.

    The issue is not that device assignment not saved, rather the device status for single-slot pool was not being handled properly resulting in confusing webGUI.

     

    > P.S. this is somewhat related to this issue, I though the cache config wasn't being saved because of the extra spaces in the device name but it was this issue, so now that I saved the new config I don't really care that the device name has an extra underscore.

     

    Totally unrelated.  Would like to get to the bottom of that one since once 6.10 stable is published issue will probably crop up again.

     

    • Like 1
    Link to comment
    JorgeB
    12 minutes ago, limetech said:

    Totally unrelated.

    Yes, I wasn't very clear, I meant related for me, since not saving the cache config was my main problem, don't really care about the name change once it's saved, but if it can be fixed good for anyone else using the same NVMe device, I'll reopen the other one.

    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.