trurl

Moderators
  • Posts

    43882
  • Joined

  • Last visited

  • Days Won

    137

Report Comments posted by trurl

  1. 4 minutes ago, foux said:

    To use docker port mappings to 80 and 443, you have to have 80 and 443 free on your host ;) 

    Why would you map container ports to host ports 80 and 443?

     

    If the container uses ports 80 and 443, you map those container ports to other host ports.

     

    The whole point of docker port mappings is to make a container use other host ports that aren't being used by something else.

  2. 1 minute ago, L0rdRaiden said:

    Should I create the zfs pool in the array section or in the pool section of unRAID webui?

    Array is still individual disks not pools. Each array disk can be a separate zfs disk but not a pool.

     

    Quote

    ZFS Pools

    New in this release is the ability to create a ZFS file system in a user-defined pool. In addition you may format any data device in the unRAID array with a single-device ZFS file system.

     

    • Thanks 1
  3. Just did the upgrade from 6.11.5 no problems.

     

    I had been sitting this one out since zfs isn't in my immediate future, but decided to get familiar with the webUI changes.

     

    One thing I noticed is my libvirt is 10G instead of 1G, looking at my backup I see 10G is what it was before so not related to upgrade. But it's not something I would have changed so I wonder how it got that way and when.

  4. 19 minutes ago, Zonediver said:

    Well... i understand, what this means - but its not necessary, because? See this...

    Your screenshot is actually the result of many iterations of changes to v6 webUI trying to help people understand. Now that you already understand it maybe it seems unnecessary to you.

  5. 8 minutes ago, trurl said:

    The old way and the new way of thinking are functionally the same

    If all you have is the array, and no cache or other pools, then your Primary is the array, and secondary is none

     

    If you have a pool named 'cache', then

    • cache:no = Primary:array, Secondary:none
    • cache:only = Primary:cache, Secondary:none
    • cache:yes = Primary:cache, Secondary:array, Mover action: cache->array
    • cache:prefer = Primary:cache, Secondary:array, Mover action: array->cache

     

    Just substitute another pool name for 'cache' above for other pools.

    • Like 1
    • Thanks 7
  6. 12 hours ago, Zonediver said:

    Now i am more confused then before... 🤪

    This is definitely an improvement. I never could think of a good way to clear up the confusion of the "old" way of thinking. I think this is it.

     

    What we have with 6.11:

    • A user share setting labeled "Use cache pool", which isn't necessarily about a pool named 'cache' since we can name pools as we wish. The 4 possible values for this setting are not self-explanatory, and has always confused new users.
    • Another user share setting labeled "Select cache pool" which is not necessarily about a pool named 'cache'. This setting is where you specify which pool that other setting is about.

     

    What we have with 6.12rc4:

    • A user share setting labeled Primary storage which specifies where new files are written.
    • A user share setting labeled Secondary storage which specifies where overflow gets written.
    • A user share setting labeled Mover action which specifies source/destination for mover.

     

    The old way and the new way of thinking are functionally the same, but the new way is much easier to explain and understand. And it provides a way forward for future functionality.

     

    • Like 1
    • Upvote 3
  7. 12 hours ago, KyleS said:

    What on earth are you talking about. There's nothing in there.

    I was trying to understand what you were talking about in your first post.

     

    Quote

    None of my shares are showing up

    We see lots of different things a user might mean by this sentence.

     

    User Shares not showing up in the webUI (often a browser problem)

    and/or

    User Share(s) not showing up on the network (could be several reasons)

    Maybe even

    Nothing showing up at /mnt/user (occasionally user shares are broken due to filesystem corruption on a disk or something)

     

    Can you understand why I didn't know what you meant at first? It took several tries to get something that made enough sense to investigate.

     

    You haven't even told us which prerelease you are using.

     

    I agree that if I create that folder it does not get displayed in User Shares (on 6.11.5).

     

    Still don't understand why you would want a user share with such a name. I'm guessing you are considering creating lots of folders with similar names as some sort of workaround. Maybe there is a better workaround such as creating a VM for handling your special case.

     

    I'm not sure this should be considered Urgent.