cjvs

New Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by cjvs

  1. So, I did a crazy hack to make this work (and it seemed to, but I can't really verify 4.85 gigs of files).  Here are my steps if anyone wants to try.

     

    This is all because clicking "ok" on syncing a non-empty folder won't work.  For this we'll assume Computer 1 and Computer 2 have a folder with identical data.  We'll call it folder1.

     

    1. Remove any references to folder1 in BTSync.

    2. Add folder1 to BTSync on Computer 1.

    3. Copy the share link.

    4. Shutdown BTSync on Computer 1 (so it doesn't start syncing until you're ready).

    5. Rename folder1 to folder2 on Computer 2.

    6. Add folder1 (which is now empty) to BTSync on Computer2 (via the share link).

    7. Shutdown BTSync on Computer 2.

    8. Copy the .sync folder from folder1 to folder2.

    9. Either delete or rename folder1, so you can rename folder2 back to folder1.

    10. Now that you have your computers set up how they should be (with BTSync references AND all of your data) you can restart BTSync on both computers.

     

    The indexing time will depend on how much data you have, but it should be substantially less than actually transferring the data.

    Had the issue on my QNAP nas with 2.0.105 too. Your way worked and saved me a lot of data copying! The only difference being that I did not shut down the computer, but quit the app on computer one (mac) and switched off the app on the qnap in the app center.

  2. On this system, BTSync-i386 version 1.4.75 crashes immediately on startup, exactly as version 1.4.72 does:

    symbol lookup error: /usr/local/bin/btsync/btsync: undefined symbol: _ZNSs4_Rep20_S_empty_rep_storageE

    The OS is what Netgear calls RAIDiator 4.2.26; it's Debian Etch (Debian 4.0) running on a ReadyNAS Pro. Kernel is version 2.6.37.6.RNx86_64.2.4.

     

    My earlier error report for 1.4.72 is here: http://forum.bittorrent.com/topic/31281-btsync-1472-crash-on-linux-i386/

     

    I got the same issue on a QNAP TS-259 PRO+ with version 4.1.0.. However, I initially downloaded the i386 version, and later retried with the linux i386(glibc 2.3) version which did not give me this error (and could start).

     

    # uname -a

    Linux NAS 3.4.6 #1 SMP Thu Jun 12 03:34:00 CST 2014 i686 unknown