Hamilcar

Problem solved with version 1.2.73. Still stuck after restarting the app !

Quick update on my issue: I discovered that the synology indexing service creates a lot of @eadir folders, so I added @eadir in the syncignore text file and now btsync is indexing the "correct" number of files ! One issue persists: btsync is stuck on "indexing" for that folder. Since I'm still not able to update to the latest version (have to wait on synocommunity to update it), I'll do another reply to see if the indexing issue is still there after updating.

Thanks for the answer, I unfortunately depend on synocommunity to update the package, so I'll try your suggestion when they have updated the package !

anyone ?

Hi, I already contacted the support team with a ticket on a previous version of btsync with this problem but I never got an answer, that's why I'm trying the forums. My problem is that btsync is indexing 660'000 files in a folder that contains 150'000 files. It eats a lot of ram, and it's stuck on "indexing" in the GUI. I'm using the synocommunity package on a DS1812+ running the latest version of DSM. BT Sync version is 1.2.72. EDIT: I've fixed part of my problem by adding a "/" to the end of the path while configuring a folder (something like: home/folder1/ instead of home/folder). BT Sync is now showing the right number of files but the synced folder is not showing the right size, I'm guessing it's just a glitch ? EDIT2: After a reboot my problem came back: indexing 600'000 + files (and stuck on indexing) instead of the 150'000 + in the folder any ideas ?

Thanks for your help, I'll send a log, see if I got it right !

I managed to create a debug. txt file, however I don't understand what "contents of FFFF" means. Can you help ?

Hi, I installed bittorrent sync (V. 1.1.70) on a synology NAS (DS1812+) via this repository: http://www.synocommunity.com/ It seems to be indexing fine but it is indexing way too much files, I have a folder with 150'000+ files in it and it is now showing 496'000+ files and now adding them really slowly, it's also eating quite a lot of RAM (600MB). I also have no idea how to send you a log. Otherwise thanks for the great program !