• Content Count

  • Joined

  • Last visited

Everything posted by KawateTadako

  1. Option to sync only when mobile device is charging from AC power. edit: nvm found the option already exist. It was kinda of hidden. Thought only option was the toggle switch but tapping title open another menu.
  2. I don't get catalogue corruption but LR does complain about previews cache problems during imports. "Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches." Don't get this problem if LR is importing and processing 1 file at a time, but if multiple imports done in parallel is done then it will. Could it be having issues with available bandwidth since my LR db and data storage is all on the LAN NAS.
  3. My 70k files via NAS SMB indexing took over 10hrs, but even with local windows SSD laptop drive it was indexing a lot. For anyone having issues with Lightroom, you need to manually extend the interval rescan time because the file count to index is high. Even on a fast local SSD, 70k files will take several minutes to scan. The default is 10 minutes interval, but if your scans take 5 minutes you'll be using 33% of the time indexing wasting CPU resources; sucks on laptops. BTsync doesn't warn you about this, most users won't know the advance settings to change. For anyone tryin
  4. Tried to attached 527MB of sync log, but couldn't. Connection was dropped for taking too long to upload.
  5. folder_rescan_interval can be edited in advanced preferences as a global setting. But, it is useful to allow individual folder specific rescan settings too. Rescan indexing can take a long time if you have lots of files. Example, I have 70K+ files in a lightroom folder, it takes 4 minutes to rescan with a fast SSD. The default rescan interval is 10minutes (600s) which means my laptop spends 40% of the time rescanning eating away battery. I don't need my lightroom folder to rescan every 10minutes, but other smaller document folders I would like to.
  6. Btsync doesn't have a limit on numbers of files to be synced, but there is a hardware limit. I have ~75K files on my SSD windows PC. It takes 4 minutes to index which is about 300 files/sec rate. The default folder_rescan_interval is 600s. Which means once I reach 180k files it will be indexing perpetually eating cpu/system resources 24/7. Was wondering why my system was slow half the time until I figured it out. I've extended the default rescan interval, but not everyone will know to. Does enterprise sync do it differently? How does it support many users? Wouldn't it be indexing al
  7. Lightroom isn't open and locking any files. I work with the Lightroom catalog on machines with SSD so I assume it index faster? It is then synced to a dedicated PC for backup which uses a network-share on freenas server as storage location. It is this PC which is taking 2hrs to index the 70k files. Are you inferring it shouldn't take 2hrs to index? I've collected 326MB of sync.logs.xxxxxxxx.zip log files for the past week since adding the Lightroom folder. Should I send all of them?
  8. I have a Adobe Lightroom folder with 70k files that is synced across my multiple computers. It takes 2hrs to index. Because it takes so long i've set my folder_rescan_interval to 72000 to limit scans to once a day. Is there any way to speed this up?
  9. version 2.3.6 with advance power user preference enable_file_system_notification disabled works for me. No longer get constant re-indexing. Freenas uses SMB 2.0 & doesn't support file system notification. What I don't get is how Sync is detecting the notification, is it falsely detecting and re-indexing constantly? So disabling enable_file_system_notification is a work around fix? Ideally, if Sync can truly detect then I wouldn't have to use the alternative method of scanning intervals.
  10. Updated to 2.3.5, still having the same issue. Left it indexing for 40 minutes before giving up and reverted back to 2.2.7 which index completed in minutes. uploaded new logs to ticket request #40669
  11. @RomanZ my FreeNAS-9.3-STABLE is running SMB2, SMB 3.0 isn't supported. I upgraded to 2.3.3 again, set "enable_file_system_notifications to false. Indexing still taking ongoing after an half hour. On 2.2.7 it only takes minutes to complete. Looking at sync.log I see OnNotifyFileChange, Journal: assign file_id, will scan folder, entry, erase file_id lines repeated for the same files over and over again. Sync.log overflows, get archived as *.zip until I have GB's of log stored.
  12. I believe there were two other files, probably .dll that I was able to delete.
  13. Windows 10 C:\Users\<username>\Appdata\Roaming\Bittorent Sync\ShellExtIO.log It remains even after uninstalling BTSync. Can't delete it. Tried rebooting still can't remove as it is in use. File gets update with new content even though BTSync is uninstalled? Some of the stuff inside it are 2016-03-11 11:55:55 (Explorer.EXE:1432) ShellDoneOverlayIcon C:\Users\PC\AppData\Roaming\BitTorrent Sync\ShellExtIO.log 2016-03-11 11:55:57 (notepad++.exe:468) ==== end ==== 2016-03-11 11:55:58 (Explorer.EXE:1432) ShellDoneOverlayIcon C:\Users\PC\AppData\Roaming\BitTorrent
  14. I am looking at the 500MB+ of sync.log.xxx.zip (that is a lot of compressed logs ) Appears BTSYNC 2.3.3 is indexing my files over and over again for hours and hours, almost all day. Something is wrong. Uninstalled 2.3.3, wiped userdata and installed 2.2.7. Added my 70GB folder to index and it finished in 8 minutes.
  15. I'm using Freenas and it doesn't support file change notification. I need to use rescan interval; I am very aware of this. I've been doing it with Version 2.2.5 for a while now fine. Indexing works and minimal load on the freenas. The problem comes when upgrading to 2.3.3. Indexing takes a very long time about half a day as indicated by the graph. Downgrading back to 2.2.5 everything is normal again.
  16. My BTSync is on a windows PC that has access to a shared folder on a NAS. If someone else on the network make changes to that shared folder, how will BTSync know to update if it doesn't scan and index?
  17. So I contacted support and their suggestion is to set rescan interval to "0" (the default is 600) This stops the constant indexing with 2.3.3 ,but also mean new files won't be indexed and synced.
  18. I use BTSYNC Pro on a windows PC, but the shared 70GB directory is on a NAS. Because of that I can't use window's OS notification system for indexing file changes. The work around is to set scanning intervals using rescan interval in Sync settings -> Advanced -> Power user. I've set it to 36000 which is fine for me. This has been working fine on version 2.2.5 Recently I've updated to the latest 2.3.3 and my NAS was giving heat warnings. Finally, found out BYSYNC was indexing very frequently and for prolong periods of time causing my HDD to spinup. Temporarily I've downgraded
  19. Tried it, exit and relaunch does indeed starts indexing. Was hoping more along the line of a command line or button to press.
  20. I have a networked shared folder setup with btsync. Real-time monitoring sync doesn't work with network share and it falls back to interval rescan of 600 seconds. Didn't want it to pull the HDD every 600s preventing it from sleeping so I set it for 36000seconds. Is there a way to force a manual rescan for when I need it to sync after adding a file manually?
  21. My CPU is stuck at 100%. profiler.dat is 1.2GB and profiler.dat.old is 2.1GB Files are rather large! Where do i send it?
  22. Anyone getting their CPU usage stuck at 100% running 2.0.120?
  23. "use notification" was an settings option to hide/show persistent notification from appearing. It was there in but is gone in Did it get moved or removed?