RomanZ

Administrators
  • Posts

    3,588
  • Joined

  • Last visited

Posts posted by RomanZ

  1. @mikedr It is not a bug, but the way how your DSM works. The fact that changes only detected during rescan on your DS214 indicate that notifications are not coming from NAS OS. The most common reasons for non-working notifications are:

    1. Files are getting changed on NAS over SMB/Samba below v3, OR files getting changed by AFP.
    2. Your NAS runs with Glibc of version 2.3 which does not support file notifications at all.
    3. You've got extreme number of folders and files in synced folders and your NAS ran out of inotify handles to track them all.
     

  2. @12345lamacun We are done with issue investigation. By some unknown reason, Raspbian for RPI1 uses ARMHF default architecture. As a result, apt-get downloads ARMHF build from our repo. This is not something we can fix as it is in Raspbian code.

    Although, you can work it around by adding additional architecture to your OS and forcing manual installation of ARMEL build:

    dpkg --add-architecture armel
    apt-get update
    apt-get install btsync:armel

     

  3. @YI WANG Do I understand correctly that you need to sync 2 folders, with pretty much same existing content between your office and home computer?

    If yes, I'm missing the point of

    Quote

    Now I usually doing now is share one folder (from client A) with owner permission, when the other client(client B) started the syncing process, I just disconnected the sync progress(client B) and link the folder which already existed on the client B( this folder is exactly the same like the one on client A). 

     

    Why not just add the folder in office, make the link or key and add same folder at home and let Sync do its job?

  4. @zkyevolved The limit you refer to is only for file size, not for the total amount of files. There is no setting that limits amount of copies in Archive. Although, there is a setting which orders Sync to clean up old archived files with age of 30 days or more. You can reduce this limit to, say, 5 days and reduce your total amount of archived data. Check the sync_trash_ttl power option - it indicates file storing period in days.

  5. @12345lamacun Gorn reported that Sync is not running on new version of Arch Linux, that's different from your issue.

    Your issue is that during installation Sync package brings your an ARMHF binary to your RPI1 while RPI1 actually does not support hard floating point operations and should get the ARM binary. I reproduced it in our lab. We'll prioritize and fix the issue eventually.

    Meanwhile, you can replace the binary /usr/bin/btsync to ARM version and use it normally.

  6. @Roberto D How do you change the files on your QNAP? Over SMB / AFP? Is the latency around 10 minutes?

    If yes, your issue is that QNAP does not send Sync file change notifications (which actually depends on how Samba and AFP daemons implemented by QNAP) and Sync detects changes during every 10-minutes rescan. In this case you can make rescan more frequent if you don't have much files. Though, it'll increase load on your HDD and prevent NAS from sleeping.

     

  7. @mr.canada How do you expect your files are going to be changed on your NAS? Over SMB? Over AFP? One of the most common issues causing non-working files notifications on NASes is the fact that files get changed by SMB or AFP daemon, not some application on NAS. Technically, if NAS supports SMB3.0 as well remote SMB client, notifications should work well. Although we never tested it in lab. Not sure about AFP.