JimmyTheSaint

Is it possibly a permissions issue? My btsync executable's permissions are 755. You can cd to that directory and do: # chmod 755 btsync Also, perhaps make sure the owner and group of the executable are correct. For example, my exectuable's owner/group are "bittorrentsync/users." To achieve that, I could do: # chown bittorrentsync:users btsync

It will only stop syncing; it won't delete the contents from your SD card. The dialog box that comes up does say that, but I wish they'd add "The folder's contents won't be deleted from your SD card."

Can someone explain the idea behind the Android backup-type sync folders? They seem to be the same as a sync that's read/write on the Android and read-only on all other devices that sync it. In addition, backup folders have less flexible usage in the Android app, which makes it easier to assure they're only used for the specific backup purpose, I suppose. So do they merely make it more convenient to do what can be done with regular syncs, or is there some bigger advantage/convenience that I haven't realized yet?

When you press the bottom right of the sync folder in the Android app to bring up the menu and choose "Delete," what happens?

I don't have this problem. How much stuff are you syncing? My phone syncs 600MB in 400 files.

I unlinked all that stuff yesterday. Today, I tried a completely different directory of 10GB, 37,000 files. No other clients are linked. After it all settled down, the btsync process stayed at 3.5-4.2% CPU. No other process is ever above 0.2%. When the webui says that btsync is indexing, I see its CPU usage is at 40%, and then it drops back to 4% when indexing is finished.

The filename of what I installed is btsync_ppc_quoriq-1.1.42.tar.gz

On my Linux NAS, I tested with a 90MB directory of about 60 files linking with two Windows and two Android clients, and it looked fine. So I added three more directories for sync of approximately the following sizes: 1) 15GB, 10,000 files 2) 760GB, 70,000 files 3) 300GB, 88,000 files When it finished indexing, I linked two Android devices without automatic sync and read-only to those three large dirs. No other clients linked to the large dirs, just the one small one. After several hours, when everything had synced and become stable, my NAS settled with the btsync process taking up about 70% memory and 45% CPU. So I restarted BTSync, and it later settled at about 35% memory and 20% CPU--still way too high. So I unlinked the 15GB and 760GB dirs, and the BTSync process's CPU usage settled at 10%, which I would think is unacceptably high. I unlinked the last big 300GB dir, leaving just the 90MB/60 file dir, and BTSync has 18% memory 0.1% CPU of my NAS's resources. That looks OK. Is such high CPU usage (20-45%) to be expected when syncing so much stuff, or is it just that it's beta and the Linux BTSync is likely to undergo substantial optimization? Is there some re-config I should try on my NAS?

That pauses everything, but I mean reproduce the same ind of download-on-demand functionality of the Android app: some folders continue to sync automatically while others don't. I don't want to have to pause all syncing for that. The point is to be able to retrieve things as needed from a 500GB directory that automatically syncs among large clients while working on a laptop with a 256GB SSD. Basically, I'm saying that the Android app's split ON DEVICE/REMOTE file browsers would be truly useful in the Windows version.

Does selecting "Use notification" in the Android app help keep the app running by preventing the system from killing or swapping it out of memory? Some apps say they need to remain in the notifications area for that reason. But I don't actually need the BTSync app's notifications. Normally, I kill the screen-hogging status bar process, and I'd like to be able to do that without an undue risk of losing sync.

The Android app allows toggling automatic sync. Is there any way to do that in Windows? That kind of download-on-demand functionality would be welcome on my laptops that have SSD's with limited space.

The guide works great, despite having to use the much-hated vi editor. When will Synology, Inc. evolve to emacs, I wonder?

At first, my S4 read the QR code fine, but now it won't. The camera keeps re-focusing and never captures the thing. Perhaps the problem only began when the app was updated. Manual entry is a real pain. I've seen this problem referred to in scattered places, so maybe it's worth devoting one thread to tracking it. My Note 2 read the QR code, no problem. EDIT: It started working. First on a different monitor, and then on my MacBook Retina where it had been failing. I suspect some Android permissions might have been involved, although I did do a reboot after enabling the BTSync app to have more permissions.

I see. It's something like: Dropbox and BTSync will propagate the same changes, and then another client's Dropbox (or BTSync, depending on order) will update and cause its own BTSync (or Dropbox, depending on order) to propogate things the other clients will see as new changes, but which aren't really. Now I'm imagining the possibility of thrashing, and so perhaps the massive conflicts you suggested. Now I'm a little scared to try it. Conflicts aren't a disaster, but they can be extremely annoying to clean up if you don't notice them right away.

I'm now also thinking of syncing my Dropbox folder in one swell foop. For safety, I could unlink Dropbox from all but one computer and let them all use BTSync, but it would be nice if that weren't necessary. I understand nothing's guaranteed and if I mess up my data, it's my fault, so please advise freely. My questions: Can someone explain why having Dropbox and BTSync sync the same folder on multiple computers would necessarily cause conflicts? I only ever make changes on one computer, in one mode at a time; I don't go back and forth between computers, Drobox's web site, an Android device, etc. In that case, assuming there are no extended network failures, I don't see how there'd be an especially higher probability of generating conflicts. Is this still a problem?

Here's the output I get from that with the current Synology system, DSM 4.2-3211: # /lib/libc.so.6 GNU C Library stable release version 2.8, by Roland McGrath et al. Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 4.3.2. Compiled on a Linux >>2.4.18-3<< system on 2009-11-11. Available extensions: crypt add-on version 2.1 by Michael Glad and others GNU Libidn by Simon Josefsson Native POSIX Threads Library by Ulrich Drepper et al Support for some architectures added on, not maintained in glibc core. BIND-8.2.3-T5B For bug reporting instructions, please see: <http://www.gnu.org/software/libc/bugs.html>.

How do you check the glibc version? Alternatively, DS213+ users can ask on the Synology forums.

Are you sure that's the correct version for the DS213+, which has a QorlQ P1022 PPC CPU?

It would be nice if someone could do a quick test so that I know it's not some quirk on my side. EDIT: I reproduced the error and submitted a log.

No special status other than the fact that the folder in question is open in a Windows file manager on one computer at the same time it's being deleted on the other. When I do the same kind of operation with my other cloud server software, no such inconsistency arises: the deleted folder doesn't get recreated on Computer1, and the deleted material no longer exists on Computer2. Even if the deleted material is still visible in Computer2's file manager, a screen refresh clarifies the situation. I assure you, it's scary. The dev reported it as fixed three months ago, and no one's contradicted that in the meantime.

I just came back to the project today with the announcement of the Android app, and the folder deletion problem is not fixed. I've set up and synced two Windows 7's and one Android, and everything works well, except: Inside my sync folder, when I delete a folder from Computer1 that is also open in the Windows explorer of Computer2, Computer2 fails to have that folder deleted. Its contents are deleted (I tested with minimal content), but the enclosing folder remains. Then that remaining folder gets recreated (empty) back on Computer1. I think it's a rather scary error because there's not telling what will happen after a session of rearranging and re-filing stuff. I mean, you're always paranoid that you left the computer at home open to a folder that might be involved in changes you want to make while you're at some remote location. The more computers you sync with (because you like to have things backed up in a few places), the scarier the possibilities get.

Testing reveals that using BitTorrent Sync in conjunction with Synology's Android apps is just too cumbersome to substitute for a real BT Sync Android app.

Thanks. Its CPU might not be new, but Synology's DS213+ is a current model.

My Synology 213+ has a Freescale QorlQ P1022 PPC CPU. I copy the PPC SyncApp to my NAS, gunzip it, and then do # ./SyncApp_powerpc but it returns "Illegal instruction." The file's permissions are 755, and I'm logged in as the root user. What am I doing wrong?

I just started using BitTorrentSync, so forgive me if this has already been mentioned, but I don't see a relevant thread. When I delete a folder on one machine, the other machine gets all the files deleted, but the folder itself remains. Also, if I rename a folder on one machine, the other machine shows the renamed folder plus an empty version of the original filename. I would hope that eventually the status of folders will be fully synced, too.