• Posts

  • Joined

  • Last visited

Everything posted by Daria

  1. Where do you attempt to move the files: from Sync or file manager application? If not the latter, try to do it from there. If this is not possible for some reason, please list all the steps, attach screenshots if they can be illustrative in this case. Any other details would be appreciated (like OS of the device on which you encounter the issue).
  2. Please send screenshots or Terminal output illustrating this. Also specify the path to the default folder location. Have you adjusted any of the parameters in Power user preferences?
  3. @k1s on which drive are there free TB? The warning says about the drive where default folder location points, see: https://help.resilio.com/hc/en-us/articles/360001217950-Core-warnings
  4. @Humpatz in this case contact Sync Support via submitting a feedback from Sync (Preferences (Settings) > Support > Contact Support).
  5. Cloning or migration of Sync instance (settings) aren't supported, this is mentioned in our KB: https://help.resilio.com/hc/en-us/articles/360018421940-Cloning-Sync The best way is to start all over again on a new device.
  6. Dear all! A universal binary for Sync on Mac has been introduced. Download Sync from our website and update the app on your Mac devices: https://www.resilio.com/platforms/desktop/
  7. This looks like a connectivity issue, here you can find the steps to troubleshoot the issue: https://help.resilio.com/hc/en-us/articles/205450205-Peers-aren-t-connecting
  8. Old version of the file is moved to Archive, located in .sync inside the shared folder: https://help.resilio.com/hc/en-us/articles/204754239-Using-Archive-for-file-versioning-and-restoring-deleted-files- This is how Sync works when processing changes to one file from several peers. When Sync encounters conflicting files, the file synced from remote is going to have ".Conflict" in its name: https://help.resilio.com/hc/en-us/articles/204753629-Conflict-files-in-Sync
  9. Dear all! We suspect that there is an issue with async disk operations that leads to Sync crashing. The suggested way to prevent it from happening is adding "async_io" : false, line to resilio-sync.conf file, like this (please mind the syntax): To find the absolute path to the file, run the following command in the terminal (Sync must be running) ps aux | grep rslsync | grep -v grep Prior to editing of the config, stop Sync.
  10. Please submit a ticket from Android device from "Help > Contact support". After tapping on envelope, agree to send logs.
  11. Is the shared folder located on SD Card? If so, disable Archive for it (toggle off ""i" > Preferences > Use archive").
  12. Please set disk_min_free_space parameter to 0 in Power user preferences (Preferences > Advanced > Open power user preferences). Restart Sync to apply the change.
  13. The issue that you encountered has been considered as bug that will be fixed in 2.7.2. Here is what you can do to upgrade to 2.7.1: 1. Stop Resilio Sync Service via Services; 2. Right-click on "Resilio Sync Service" in Services - in "Path to executable" you should see path to exe file: "C:\ProgramData\Resilio Sync Service\Resilio Sync.exe". 3. Rename previously downloaded installer for 2.7.1 to Resilio Sync.exe and move it to "C:\ProgramData\Resilio Sync Service", replacing previous "Resilio Sync.exe" file; 4. Start Resilio Sync Service again.
  14. @Henry 53 Please contact Support sending .dmp files that can be found in one of the locations listed here: https://help.resilio.com/hc/en-us/articles/206214615-Collecting-crash-reports-mini-dumps-and-core-dumps
  15. @dankshit The file was added to directory tree. Sync doesn't remove it from there despite the fact that the file wasn't synced across other peers. So, this warning is a false-positive that can be disabled by setting enable_warning_no_source to false in Power user preferences (Preferences > Advanced):
  16. @MichelV We may assume that this is due to Sync's re-scan for any modifications and changes of files inside share(s). If any file is tracked as changed, Sync re-hashes it to detect what piece of file got changed and needs to be synced. By default, this re-scan takes place every 10 minutes. If you want us to take a closer look, submit new feedback from Sync via Preferences > Support > Contact support with checking the box "Include logs".
  17. @marbb00 Synchronization between two peers requires both of them being online, since there is one source peer. So, syncing between two systems on one PC won't work, since while Ubuntu is online, Windows peer is offline. When you connect peer with link, it will say "Pending Approval", even if you unchecked such option due to a simple fact - source peer is offline. Are you sure that Sync stayed on pending approval, when you tried to connect using a key? Generally, it says "Not synced yet". You also mention that the folder is connected with some other PC as well. Was this PC online when you shared a key with Ubuntu? If no, try it out.
  18. @dtorrey Archive folder can be found inside hidden .sync directory within the share. It can also be accessed via Sync UI - go to Share's Options (vertical ellipsis) > Open archive...
  19. This is covered in our KB article, please check "Restoring Files from Encrypted Node" part: https://help.resilio.com/hc/en-us/articles/207370466-Encrypted-folders
  20. If you want to sync a folder between two PCs, you don't need any other devices. Of course, synchronization requires at least one source peer to be online so that destination peer got the data.
  21. @sven9191 Can you please specify Sync version on NAS (check via App Center)? Also, please attach screenshots of the pages showing the errors.
  22. @Andy+ Unfortunately, we cannot provide you with any backstage details regarding the release for now. One thing is certain - the team is working hard on it. All important info should be included in change log and covered in the dedicated topic as usual, when the release comes out. Sync is not abandoned, all encountered issues are being actively addressed.
  23. @SirKronos Thanks for your suggestion! Your concern is reasonable, will look about its implementing, but no ETA can be provided. xattr fix has been included in the upcoming release.
  24. @SirKronosThere were no alert since Sync was working on syncing those ResourceFork items. Sync stuck on 99% since extended attributes (which ResourceFork is) were different on source and destination peer - whenever such difference occurs, synchronization happens again and again until the match. Andy is right here: 99% in Status was a warning sign. Really sorry for the caused troubles!