• Not a bug report per se, but it does bug me (and would be easy to 'fix')


    Marshalleq
    • Minor

    If fix common problems is going to constantly tell me that I must select RW/Slave mode in all my file access paths in docker, why isn't it just set like this as default?  Seems obvious and probably very easy to implement.  What am I missing?  When should I not use a slave mode access?




    User Feedback

    Recommended Comments

    Yes this is only needed for UD as it mounts the drives after the docker service is started. At least it was in that order before. 

    Normal array starts before docker is started and does not need the slave option. 

    Link to comment
    10 minutes ago, Marshalleq said:

    UD = Unassigned Disks?  Then I guess it could be defaulted for unassigned disks?  

    Probably won't happen, if only because unRaid itself does not support unassigned disks.  That only happens via the UD plugin.

    Link to comment

    OK, so feedback for the plugin perhaps, to default the Unraid behaviour.  I only need to do this because Unraid does not support SSD's in an array, if it did problem would be solved.

     

    And I don't want to add it to the cache, as it's an enterprise SSD I use for dockers and raid which handles the IO of those things much better without killing the SSD.

     

    Unless you've got an idea I haven't thought of?

    Link to comment

     

    14 minutes ago, Marshalleq said:

    Unless you've got an idea I haven't thought of?

    Don't lose sleep over it.  I forget to set slave all the time.  FCP reminds me on the next scan.  That's what it's there for - To let you know of a mistake.  The only downside of not setting slave is that under certain circumstances, your files within the UD mount will not be visible to the container.  But, there's no data loss, in that circumstance, and a simple edit of the container to set slave mode fixes it permanently.

    Link to comment
    43 minutes ago, Marshalleq said:

    Unraid does not support SSD's in an array

    It supports SSDs in the cache pool and probably most use the cache pool instead of UD for dockers.

    Link to comment

    Then don't use cache for your shares (no cache, no mover, direct writes to array) and use the pool only for docker and VM's.  Keep in mind, that if you put your docker image or VM's in array, than every write will involve parity(s).

    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.