Jump to content

trurl

Moderators
  • Posts

    44,012
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. According to those earlier diagnostics, your appdata and system shares have files on the array.

     

    Ideally, appdata, domains, and system shares would have all files on cache or other fast pool with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

     

    Also, why do you have 500G docker.img? Have you had problems filling it? The usual cause of filling docker.img is an application writing to a path that isn't mapped.

     

    Your docker.img was only using 18G in those diagnostics. Probaby 30G would be more than enough. And it should be on a fast pool with the rest of the system share.

  2. These are the only shares you have configured to be moved from cache to array:

     

    isos                              shareUseCache="yes"     # Share exists on cache, disk2
    m---a                             shareUseCache="yes"     # Share exists on cache, disk1, disk2, disk3
    

    There are some other shares you should have configured to stay on cache, but we will get to that after you have room on cache.

     

    Mover won't replace files, so possibly you have some cached files that are already on the array.

     

    Enable mover logging in Scheduler Settings, try mover again, then post new diagnostics.

  3. 2 hours ago, Samsonight said:

    all non-cached (/mnt/user0) files and folders.

     

    And then using a script to move the most accessed files to the (unraid) cache (/mnt/user).

    /mnt/user is the user shares including all pools. You would have to specify /mnt/poolname, such as /mnt/cache, for the move destination.

     

    You definitely don't want to try to move anything from /mnt/user0 to /mnt/user. That would almost certainly result in lost data.

  4. 18 minutes ago, MATTK said:

    5 USB 3.0 HDDs, one of them set as a parity drive

    USB not recommended for array or pools for many reasons. Spindown might be one of those reasons.

     

    17 minutes ago, MATTK said:

    tried stopping all Docker and VM services

    Shouldn't matter, since it looks like those shares are configured to stay on cache anyway.

×
×
  • Create New...