Arragon

Members
  • Posts

    42
  • Joined

  • Last visited

Posts posted by Arragon

  1. 5 hours ago, BVD said:

    The problem insofar as I'm aware is/was related to automatically created snapshots of docker image data (each individual layer of each image), to the point that the filesystem would start encountering performance issues. Basically so many filesystems ended up getting created that the system would grow sluggish over time.

    Haha, who would do that.  *hastily deletes 51000 Znapsend snapshots*

    • Like 1
  2. 44 minutes ago, alturismo said:

    and may before you didnt thought about it, no igpu available for transcoding ?

    I believe the AMD Ryzen 5 3600 has no integrated GPU and the board only has on PCIe x16 Slot (and 2 x1 Slots)

     

  3. 44 minutes ago, trurl said:

    But won't perform as well due to slower parity, and will keep array disks spinning since that file is always open.

    Since the user asked for a server with SSDs, I did assume he wouldn't put some spinning rust for that obligatory array drive.  And with a single drive, there is not parity

    image.png.154a40603520db491e3a1833e6394406.png

  4. 32 minutes ago, ich777 said:

    Please keep in mind that this documentation is for stock unRAID systems

    [...]

    As you can see it is using the ZFS driver automagically.

    Of course Limetech would not account for ZFS since it is not officially supported.  But since I was not sure about docker picking the right storage driver and my previous attempt with unstable builds (2.0.3 iirc) was unsuccessful, I recommended setting the docker vDisk location to path on the array which 100% does work.

  5. 7 minutes ago, ich777 said:

    I don't understand, what is not recommended or where does it say it's not recommended?

    it says

    Quote

    In a specified directory which is bind-mounted at /var/lib/docker.  Further, the file system where this directory is located must either be btrfs or xfs.

    zfs would have zfs storage driver instead of the btrfs or overlay2 one

  6. 2 hours ago, ich777 said:

    Please try to use not an image, use a Docker path instead, have no problem using everything on a zpool, currently I'm using ZFS 2.1.1 on unRAID 6.10.0-rc1

     

    Limetech does not yet recommend this (https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.0#Docker)

    I think it would be best if we could get it to work with the ZFS storage driver (https://docs.docker.com/storage/storagedriver/zfs-driver/) once ZFS is officially in Unraid.

     

    @ich777what does 

    docker info

    give you for your setup? Did it autoselect zfs as storage driver?

  7. You should have a single drive for Unraid's array, so the system can start since most services need the array started.  Also your docker.img should be placed on this drive as was witten earlier.

    I have atime off in general and setting autotrim on for SSDs is something I just do like setting ashift manually on creation.  For the compression I would go with zstd instead of lz4 however.

    • Like 1