RomanZ

Hi all, Here is package with fixed issue for all QNAP nases based on x86 CPU. Could you please check if now it installs and works fine? Download link

@cbmainz Yes, it is true for both Sync for Business and Sync for Individuals. Generally, Sync is using same core with same encryption algorithms.

@dazdingo There were couple of proposals from people, although it doesn't look like it get a big interest. You can browse forum for cloud tag for more info.

@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.

@patho That's the package demand. We'll fix it and you'll be able to install armel pacakge on your RPI1. Stay tuned for updates. The bittorrent-sync-pi-server_2.3.7_armhf.deb package actually contained ARMEL binary - I just checked. That's why it ran on your RPI1. ARMHF can't run on RPI1 - it contains instructions that CPU can't interpret.

@eldrin Should be fixed in 2.4. In 2.4, file is rotated at 100Mb.

@rousern7 Indeed, this is due to fact that you've got interfaces linked in bridge. As a quick solution, you may unlink interfaces. We'll check how this can be fixed in code, although fix won't be in closest releases.

@DeAnn I can see that you've turned to our support - please follow our instructions. We'll do our best to provide you easy guidance.

Dear community, The issue with QNAP packages is being investigated and will be fixed soon. Meanwhile, you can use last version of Sync 2.3.8 which can be downloaded here.

@eimer No, it's not the same issue. All you need to do is allow Syno to install non-signed pacakges. Check this KB article for solution.

@rousern7 For norbert78 that was an issue with configuring his adapter. Nothing we can deal with. Unfortunately, he did not respond how did he manage to solve the issue. for mfresco the issue was that the name of his adapter was not the standard one "en0, en1 ..." for Mac, but "bridge0" instead. Could you please share your ifconfig output?

@bumper86 Synology published wrong build for ARMADA* architectures. We are working with them to get it fixed. Please install this build thru manual package installation.

@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

@Roberto D In any case, it is highly not advised to add to Sync any folders, added to other syncing / cloud solutions. Neither we are nor other vendors are testing such scenarios, so some interoperability issues may occur.

@patoka How many files do you sync and what is the size of RAM on your laptop?

@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 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?

@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.

@Roberto D I checked it in our lab - QNAP itself can see the files with no issues (File Station). Keeping in mind that Sync is using standard POSIX to access file system - no any hacks - it looks to be some issue with the app that can't see files delivered by Sync.

@OttoTheBusDriver Send us debug logs from your NAS. Just file a ticket with logs and we'll check what's going on.

@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.

@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.

@mr.canada JFYI - be aware of the fact that Samba daemon doesn't like when someone else accesses files it possess ;). Read more here.

@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.

@12345lamacun We didn't get any reports on issues of Sync working on Raspbian for RPI1. The ARMHF build should run just fine. What's your issue? Is it reporting some error or crashing?

@JJMcKay Not actually. It just indicates that some files are locked by another processes and Sync can't access them, and allows to precisely locate these files. It's not a collaboration feature, allowing to prevent other peers to block file opened by a user.