atte

Don't know how many files are in the sync folders, though. How can I find out via the ssh terminal?find -type f -print | wc -l

atte@hanstholm:/mnt/usb/atte/hanstholm/medium$ find -type f -print | wc -l322594 Banana Pi looking real good! http://www.reichelt.com/Programmer-Development-Tools/BANANA-PI/3//index.html?ACTION=3&GROUPID=5100&ARTICLE=144326&OFFSET=16&&SID=13U8kNp38AAAIAACV128A4727383813fdeb59295dcd60178b53a0&LANGUAGE=US

I'm very enouraged by your reply, it seems it's indeed possible to run btsync on the pi! Sure I've rebooted and/or restarted the btsync... Did you install via the repo (http://forum.bittorrent.com/topic/18974-debian-and-ubuntu-server-unofficial-packages-for-bittorrent-sync/) or by hand? What's the version of your btsync? Is your pi overclocked? Here's my only enabled .conf, maybe I could have a look at yours? { "device_name": "hanstholm", "listening_port" : 0, "storage_path" : "/home/atte/.btsync", "check_for_updates" : false, "use_upnp" : true, "download_limit" : 0, "upload_limit" : 0, "webui" : { }, "shared_folders" : [ { "secret" : "----", "dir" : "/mnt/usb/atte/hanstholm/medium", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : true }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/medium/music/mp3_local/btsync", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/medium/music/mp3_local/btsync/a773", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/medium/music/synth/aspect/Presets/atte", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/medium/music/synth/ams/atte", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/large/photos/btsync/atte", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/large/photos/btsync/britt", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/large/britt/downloads", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/medium/music/undervisning/elektronisk_musik/btsync/", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false }, { "secret" : "---", "dir" : "/mnt/usb/atte/hanstholm/btsync/software", "use_relay_server" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : false } ]}

Hi It seems the raspberry pi is simply not fast enough to handle my 140G with btsync. At least it's been indexing away for over a week and it's still 77.6G short... So, what other options (preferrably low power and cheap) do I have? would a NAS be a better option? Which model(s) would be easiest to work with (for instance install linux on) and what are the power consumption? Thanks!

Thanks, feeling stupid here...

Thanks! This would leave unused .db* in .btsync, but I assume those would not be updated anymore, and so after a week it's pretty obvious which ones are in use... What about the .sync dir in the root of the added folder, it's no problem when re-adding, that this (and maybe other) traces of a previous sync is present in the folder?

How do I find out what version of btsync is runnning beneath btsync-gui?

I have three clients that seems to have gotten a bit confused, at least they each state that one secret (143G) is unsynced, and leaving them on for a loooong time doesn't help. What's the easiest way to the secret in question on all three nodes? Could it for instance be done by deleting one of the .db* files in .btsync? How do I find the right one? I'm on linux running btsync-gui version 0.8.5-1 installed from debian repos (not sure how to deduct the actual btsync version)

I like the "yet" part, gives me hope

Off course, I messed it up, should have been: sudo echo fs.inotify.max_user_watches=1000000 >> /etc/sysctl.conf

(still) crashes on my geode CPU. I send you logs already....

This should work no matter what your IP is: http://localhost:8888/gui/ But, as I said, it won't work if you have shared_folders defined in config file...

When you have defined shared folders in the config file supplied with --config you the web UI is disabled. So you need to add another stanza for the second folder similar to what you have with/home/user/bittorrent/sync_test Careful with the syntax, it goes a little like this: "shared_folders" : [ { "secret" : "Secret1", "dir" : "/dir1", "use_relay_server" : true, "use_tracker" : true, "use_dht" : false, "search_lan" : true, "use_sync_trash" : true } , { "secret" : "Secret2", "dir" : "/dir2", "use_relay_server" : true, "use_tracker" : true, "use_dht" : false, "search_lan" : true, "use_sync_trash" : true } , { "secret" : "Secret3", "dir" : "/dir3", "use_relay_server" : true, "use_tracker" : true, "use_dht" : false, "search_lan" : true, "use_sync_trash" : true } ]

Hi I stumbled across these posts today: http://askubuntu.com...ax-user-watches http://paulphilippov...filesystem.html http://blog.foogaro....ng-problem.html Basically: as default most (my) linux systems are limited as to the number of "watches in inotify", one of my boxes had it set to 8192. To find out your current setting: cat /proc/sys/fs/inotify/max_user_watches To change to something big: sudo echo 1000000 >> /etc/sysctl.conf All this is fine. My question, however, is: how does all this affect the way btsync runs? From reading about the lack of instant sync on BSD, it seems btsync relies on inotify to keep track of local changes that should be synced to connected boxes, so I guess it should have some impact...

1.1.40 seems to get stuck here. Have two linux boxes sharing three folders ("small", "medium" and "large") that all originated from box A. All folders are indexed on box A. Folder small is synced to box B, folder medium is in progress, and folder large is not started. Box B has been turned off during the night, when it first came up this morning, it just sat there, web interface on box A showed that 76 GB of medium folder needed to be synced to B, but no traffic... EDIT: After restarting btsync on box B the web interface on A shows that btsync thinks that 2.5Gb of "small folder" is not to be uploaded to box B. Still no traffic. And why is btsync on box A (lenovo laptop x61s) taking 6-10% of my CPU just sitting there? And just as bad: btsync suddenly want's to reindex the untouched small folder on box A....

Still crashes on my geode CPU. Did you have time to look into the logs I send you and/or try building a binary with "-march=geode"?

I really wish btsync were open source, I'm sure I'd be able to help solving my own problems...

Hi Unfortunately this also crashes on my Debian install/geode CPU. Could you try compiling with either "-march=geode" or "-march=i486 -mtune=geode" (gcc options)? Maybe "-march=i386 -mtune=geode" would make the i386 and glibc23_i386 builds work on everything they work on now + the geode, if you want to keep binaries to a minimum... I guess the best would be to use "-march=geode" and make it available as a seperate download... Hope you're willing to give this a try :-)

I tried the i386 and glibc23_i386, and they both segfaults. I cant provide logs ATM, i did this over ssh from my Phone. Pretty sure i did everything right, though...

I only used btsync since 1.1.25 or something like that. Can I download 1.0.x somewhere to try?

Happy to discover there was a new version, upgraded to 1.1.30, still crashes on my debian box with geode CPU I suspect it's a simple matter of a switch to the compiler that makes btsync incompatible with the CPU. Could you please try to make a binary that is compatibel with the geode. Thanks in advance!

I have a problem with 1.1.27 as described here: http://forum.bittorrent.com/topic/21322-btsync-coredumps-on-debian-wheezy/ Quick recap: It's a fit-pc running debian, the problem is that btsync exits with "Illegal instruction" after about a minute. Here's som info from the box: cat /patte@vodskov:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping : 2 microcode : 0x8b cpu MHz : 499.887 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips : 999.77 clflush size : 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: atte@vodskov:~$ uname -a Linux vodskov 3.2.0-4-486 #1 Debian 3.2.41-2+deb7u2 i586 GNU/Linux atte@vodskov:~$ /lib/i386-linux-gnu/libc.so.6 GNU C Library (Debian EGLIBC 2.13-38) stable release version 2.13, by Roland McGrath et al. Copyright (C) 2011 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.4.7. Compiled on a Linux 3.2.35 system on 2012-12-30. 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 BIND-8.2.3-T5B libc ABIs: UNIQUE IFUNC For bug reporting instructions, please see: <http://www.debian.org/Bugs/>. I've PM'ed kos13 a core dump.

But with .Syncignore something along those lines could be achieved. When a btsync binary is released that doesn't crash on my geode CPU, I'll investigate...

cat /patte@vodskov:~$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping : 2 microcode : 0x8b cpu MHz : 499.887 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips : 999.77 clflush size : 32 cache_alignment : 32 address sizes : 32 bits physical, 32 bits virtual power management: Ok, so I'm hoping for a binary compatible with my CPU... Silly problem, actually, if btsync were open-source, I could just go ahead and compile a working binary myself.

If I run with option --nodaemon both versions terminate with Illegal instruction NB: This is with version 1.1.27