lpa

Members
  • Content Count

    4
  • Joined

  • Last visited

About lpa

  • Rank
    New User

Profile Information

  • Gender
    Not Telling
  1. I think I may have found the problem. "storage_path" directory was not writable for user that runs btsync. And if it is empty, it tries to create directory ".sync" where binary is located, on Arch system it is /usr/bin. This directory, of course, is not writable for user. Systemd journal indicated following problems: SyncDb: failed to begin transaction to save metadata - 21Failed file save: /usr/bin/.sync//sync.dat.newShutdown. Saving config sync.datFailed file save: /usr/bin/.sync//settings.dat.newSo I changed storage_path value to "/home/user/.sync" and everything worked. Have not seen fi
  2. All due respect, I do not need a lesson on Windows vs. Linux filename limitations. As I said earlier, the filenames are fine. I will try to illustrate with an example. Laptop was offline, I changed text file "test", turned on laptop it sent old version of "test" back to other nodes. The outputs are from each machine. Laptop before turning on btsync: lpa@laptop % stat test File: ‘test’ Size: 3 Blocks: 8 IO Block: 4096 regular fileDevice: fe06h/65030d Inode: 13635201 Links: 1Access: (0644/-rw-r--r--) Uid: ( 1000/ lpa) Gid: ( 100/ users)Access: 2013-10-03 19:30:49
  3. No. Happens to all lowercase. Besides, other Linux hosts would behave same if it were case sensitivity issue.
  4. BTSync overwrites newer files with older ones. This happens if files have been modified while one client is offline. When that client comes online BTSync overwrites files with that client's (old) versions. Why? When I look at .SyncArchive on other clients I can see the deleted newer files with newer modification times than the old file, which overwrote them. I have 4 machine setup: 1 always online, Linux (server); 2 mostly(just occasional restarts) online, one Linux, one Windows; 1 laptop, online when needed, Linux. (this is the client, that propagates old file versions) All 3 Linux mach