• Content Count

  • Joined

  • Last visited

Everything posted by iaw4

  1. I am very pleased with resilio-sync. there are some not-so-intuitive aspects in adding peers and troubleshooting that could be made clearer with better messages, but overall it is awesome. I use it on 2 Macos computers and 4 linux computers, with different folders shared. I am usually the only regular user on these computers and I have sudo access on them. all my resilio-ed directories are under my main user directories, something like /home/me/... or /Users/me/... . my uid is typically 501 under macos and 1001 under linux, because these are the defaults for the first created user.
  2. weirdly, nothing. and weirdly, it started to work again, again nothing. this is why a step-by-step guide to checking where it is stuck (or a shell script) would be great.
  3. ...but now I have a connection again, though from another peer. this is very confusing. the network was up all the time, so this was not it. A troubleshooting procedure would be a great help.
  4. a resilio sync peer that used to work. now it no longer does. it has a correct key. but the peers think it is offline now (they know it exists.) this is a linux machine. I have had sync failures in the past because of permissions, but because of the offline message, I do not think this is the case. looking at the rslsync , the last messages look like this: [20170518 19:31:48.889] Relay: Connection to the relay[] has been lost with error: 104 (Connection reset by peer) [20170518 19:31:48.914] D! 10SyncTcpReq[0x00007f26344b90a0]: EOF - error: 103 (Conne
  5. rather than guess whether I have everything set correctly, it would be nice if I could write $ resilio-check-permissions ~/myfolder/ on a local computer, and resilio-check would contact the daemon to try to write a file, check for its existence, and then delete it again, telling me whether permission problems prevented functioning. /iaw
  6. on examination, the Archive is fairly small. most of the space is consumed by .!sync files. what are they, and can they be removed or trimmed? Update: Deleting them and restarting resilio seems to just rebuild them. I am now back over 60GB already...
  7. I have the following odd situation: # du -h -d1 bitsync 160G bitsync/.sync ... various 194G bitsync can I remove the .sync directory? or the archive subdirectory in .sync? if I remove it on one machine, will it remove on the others? (I think I need to figure out a way to store the history of files elsewhere. I was also looking at a GUI way to turn on/off archiving; is it in advanced?) is there some general advice on how to handle archiving (e.g., and trim/remove/move files after x days automatically)? /iaw
  8. not yet. :-). good to know. alas, the gui should be a little more userfriendly in this respect and filter what is of relevance a bit better. it could show the names of the connected hosts, rather than just a number. it could display the last error if something failed (e.g., permissions, out of space, etc.). it could display the last few files synched if one double clicks on the directory. wading through admin sync files is not great. otoh, given that a lot of info is already there, enhancing the gui should not be hard.
  9. for me, the best aspect about resilio sync is that it is the *only* filesync solution that does not mess up symbolic links. for me, the worst aspect is that the warning and error messages are not verbose enough. when two folders do not sync, please tell us why. is it a permission issue? is it a directory existence issue? is it something else that is stranger? when it says "not enough free space on the drive," add how much there is and how much it needs, and on what host the problem lies. can I see on all hosts which of my hosts has the problem? (could be in a hidden .resilio-warni
  10. there is an old rsync confusion, where adding a "/" on the directory could mean totally different things. for rsync, one does a dry-run (-n) to make sure one has it right. a small confusion can easily end up with gigabytes of duplicates. for resilio sync, this is more difficult. suggestion: on an initial synch, I would suggest three things: IF the destination folder is non-empty, collect info on how much needs to be actually transferred. after the reconciliation calculation, confirm with the user whether (s)he really wants to transfer move 100,000 files in 1 TB. similar