Speed issue when Using "mnt" storage to keep all data #203

Activity

1. AndrewAdventure

   added

   bugSomething isn't workingSomething isn't working

   on Sep 23, 2026
2. mighty-sponge commented on Oct 7, 2026

   

   mighty-sponge

   on Oct 7, 2026

   Contributor

   More actions

   Hi @AndrewAdventure, thanks for the report!

   This doesn't look like a bug in any-sync-dockercompose. STORAGE_DIR is just a bind-mount path, and every service mounts it the same way. So the only difference between ./storage and /mnt/anysync/storage is the disk/filesystem underneath. The stack (MongoDB, any-sync-node storage, Garage metadata, etc.) does a lot of small synchronous writes (fsync). It runs very slowly on storage with high fsync latency: NFS/SMB shares, HDDs, ZFS with sync=always and no SLOG, or FUSE filesystems (mergerfs, rclone…).

   Could you share what is actually mounted at /mnt? Inside the LXC:

   findmnt -T /mnt/anysync/storage
   df -T /mnt/anysync/storage

   And on the Proxmox host:

   pct config <CTID>

   Recommendation: keep STORAGE_DIR on a local SSD (e.g. the container rootfs or a Proxmox mount point backed by local SSD storage). Please avoid network shares in particular. Besides being slow, MongoDB and the node databases can get corrupted on NFS/SMB because of file-locking issues.

   If you need to keep bulk file data on the slower /mnt disk, the only part that tolerates it is the Garage object data. You can move just that via a docker-compose.override.yml and keep everything else on SSD:

   services:
     garage:
       volumes:
         - /mnt/anysync/garage-data:/var/lib/garage/data