• Incorrect share "write settings to" in RC4


    custom90gt
    • Minor

    Sorry this may be a difficult thing to explain.

    I have multiple zfs pools and a USB drive as my "array." After upgrading to R4 I have to reset settings for all of my shares. If I select one of my zfs pools labeled "zfs" and apply the settings and then click write settings to the other shares it applies another zfs pool "cache" to the selected pools.  I tried it a couple of times but it does the same thing.  I can attach pictures if that helps explain things.




    User Feedback

    Recommended Comments

    Please add more information, like screenshots of what you are trying to do.

    What are the source settings? What are the destinations? What are the results?

     

    Using the "Write" function to copy settings from source to destination(s) works as expected for me.

     

    Link to comment
    4 hours ago, bonienl said:

    Please add more information, like screenshots of what you are trying to do.

    What are the source settings? What are the destinations? What are the results?

     

    Using the "Write" function to copy settings from source to destination(s) works as expected for me.

     

     

    Maybe difficult to fully explain, but here is what I did:

    1. In one of my share folders (documents) I selected my ZFS pool as my primary storage pool.

    2. Hit apply.

    3. Utilized the write settings to function to try to copy the settings to other applicable shares (games, movies, etc).

    4. Checked the shares that I attempted to apply the settings to and they were set to "cache" instead.

     

    I tried it multiple times however it kept them as cache and not ZFS.  I just tried the write settings to function again and it kept the primary storage as ZFS so maybe it was just a fluke?  Just a minor annoyance having to manually set the primary storage location on 20+ shares manually.

    Primary Storage.png

    Link to comment

    The WRITE operation does not change the primary location, it only changes the settings related to the share allocation.

     

    • Like 1
    Link to comment
    16 minutes ago, bonienl said:

    The WRITE operation does not change the primary location, it only changes the settings related to the share allocation.

     

     

    Well that makes sense, odd that it seems to have updated them from array to cache though.  Or maybe that's my imagination.

    Link to comment
    3 hours ago, custom90gt said:

    Well that makes sense, odd that it seems to have updated them from array to cache though.  Or maybe that's my imagination.

     

    Would you be able to setup a new share and then do before and after screenshots showing what changed and then describing what you expected to change?

    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.