trurl

Moderators
  • Posts

    43837
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. 12 minutes ago, trurl said:

    Nothing can move open files. Disable Docker and VM Manager in Settings. 

     

    Also, Mover ignores any share where there is no Mover Action specified, which is what you have for all of those.

    appdata                           shareUseCache="only"    # Share exists on cache, disk4
    domains                           shareUseCache="only"    # Share exists on disk4
    isos                              shareUseCache="only"    # Share exists on disk4
    P-------e                         shareUseCache="no"      # Share exists on disk3
    P---------V                       shareUseCache="no"      # Share exists on disk4
    system                            shareUseCache="only"    # Share exists on disk4

    They need to be Primary:cache; Secondary:array; Mover Action:array->cache

  2. 53 minutes ago, goinsnoopin said:

    Last check incomplete on Tue 26 Mar 2024 06:30:01 AM EDT (yesterday), finding 25752 errors.
    Error code: -4

    That seems to correspond with when parity check was paused.

    Mar 26 06:30:01 Tower kernel: mdcmd (39): nocheck pause
    Mar 26 06:30:01 Tower kernel: 
    Mar 26 06:30:01 Tower kernel: md: recovery thread: exit status: -4
    

    Later on syslog says

    Mar 27 00:30:01 Tower kernel: md: recovery thread: check P Q ...
    ...
    Mar 27 03:57:12 Tower kernel: md: sync done. time=12431sec
    Mar 27 03:57:12 Tower kernel: md: recovery thread: exit status: 0
    

     

     

  3. appdata, domains, and system shares have files on the array. In fact, you have domains configured to be moved to the array.

     

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

     

    Mover won't replace files, so if something exists on both cache and the array you will have to decide which to keep. Dynamix File Manager plugin will let you work with folders and files directly on the server and can help you figure that out.

     

    And, from your previous diagnostics, it looks like default 20G docker.img would be more than enough. After you get those shares moved and configured correctly, you can delete, recreate at 20G, reinstall containers.

     

    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file

     

    https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications

  4. What happens if you boot in SAFE mode?

     

    On 3/25/2024 at 3:50 PM, rvijay007 said:

    Trying to manually invoke the Mover never seems to move any files

    Doesn't look like there is anything for mover to do currently.

     

    However, you need to reconfigure system share so it gets moved to cache. And nothing can move open files, so you have to disable Docker and VM Manager in Settings to get those moved.

  5. /usr is a folder in the OS, which is in RAM.

     

    The user shares are at /mnt/user.

     

    The system user share only has docker.img and libvirt.img in a default setup. This is actually specified in Docker and VM Manager settings and so is under user control.

     

    And of course there is nothing to prevent users from putting other things in the system share so no way for me to know whether you had anything else in there or not.

     

    appdata, domains, and system user shares by default are setup to live on cache pool, so Dockers/VMs will perform better and so array disks can spin down since these files are always open. This is also under user control since you can change this and specify other shares or disks for these, in Docker and VM Manager settings, and even for specific containers or VMs.

     

    Best if you don't enable Docker or VM Manager until you have cache or other fast pool setup, or these will get created on the array instead.

    • Thanks 1
  6. 8 minutes ago, Civic1201 said:

    I want to keep that shares on my cache drives only

    You should want appdata, domains, and system shares with nothing on the array so Dockers/VMs will perform better and so array disks can spin down since these files are always open.

     

    On the User Shares page, you can click Compute... for a share to see how much of each disk/pool is used by a particular user share.

  7. 9 minutes ago, MrCrispy said:

    even standard SATA has much higher write speeds. There are posts here where people have done plenty of tests and the conclusion was the smb and FUSE in unraid was to blame, without that they got much higher speeds, without using any cache.

    Realtime parity updates are the reason writes to the array cannot be as fast as SATA or even HDD speeds.

     

    https://docs.unraid.net/unraid-os/manual/storage-management/#array-write-modes

     

    And also the reason Unraid can allow different sized disks in the array.