I was able to spin up seafile-12, but it's spinning up my drive constantly.

Is there a way to map that particular directory to cache from unraid's docker settings?

I was able to do this with frigate, but frigate's directory tree was much simpler.

If I were to do the same method with seafile, I'd have to clutter up the shares.

If /seafile is already mapped, would there be a conflict if I added another mapping of:

/seafile/seafile/conf and /seafile/seafile/logs and point them to stay in cache?

Side question, does another service like nextcloud respect hdd activity and spin down when not in use?

Edited June 20, 20251 yr by EcN

use /mnt/cache/... instead of /mnt/user/...

And/Or set the share to be primary storage cache and secondary storage to none. You will have to move that share to cache first.

Edited June 20, 20251 yr by MowMdown

Currently you have it set to "Cache -> Array" so mover will move data off of your cache pool onto your spinning disks.

Switching this to "Array -> Cache" will move the data back if it's not in use when mover operates.

Edited June 20, 20251 yr by MowMdown

19 minutes ago, MowMdown said:

Currently you have it set to "Cache -> Array" so mover will move data off of your cache pool onto your spinning disks.

Switching this to "Array -> Cache" will move the data back if it's not in use when mover operates.

If I switch to array -> cache, wouldn't my media files also end up in cache? I just want the logs to go to cache since it's being accessed so often.

I just wish seafile had its logs in the appdata instead of the same directory as storing media files as well.

Edited June 20, 20251 yr by EcN

That would be correct everything within seafile would be stored in the same place.

Any solution to map ONLY /seafile/seafile/conf and /seafile/seafile/logs to point them to cache only?