KawateTadako

Members
  • Content Count

    29
  • Joined

  • Last visited

About KawateTadako

  • Rank
    Member

Recent Profile Visitors

500 profile views
  1. KawateTadako

    Lightroom Catalogue Corruption

    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.
  2. KawateTadako

    Lightroom 70k file folder takes 2hr to index

    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 trying to use SMB on a NAS share, skip it, indexing is way too slow. I ended up abandoning it. Resorted to creating a windows VM with Dynamic VHD image stored on the NAS. This way the data is still stored on the NAS, but btsync still see it as a NTFS drive.
  3. KawateTadako

    Lightroom 70k file folder takes 2hr to index

    Tried to attached 527MB of sync log, but couldn't. Connection was dropped for taking too long to upload.
  4. 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.
  5. KawateTadako

    Syncing file number limit

    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 all the time spinning the drives?
  6. KawateTadako

    Lightroom 70k file folder takes 2hr to index

    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?
  7. KawateTadako

    Lightroom 70k file folder takes 2hr to index

    Windows 2.3.8 (560)
  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. KawateTadako

    Frequent and long indexing stressing HDD & CPU

    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. KawateTadako

    Frequent and long indexing stressing HDD & CPU

    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. KawateTadako

    Frequent and long indexing stressing HDD & CPU

    @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. KawateTadako

    What is ShellExtIO.log? Can't delete it

    I believe there were two other files, probably .dll that I was able to delete.
  13. KawateTadako

    Frequent and long indexing stressing HDD & CPU

    forum.getsync.com/topic/41708-latest-desktop-build-227
  14. 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 Sync\ShellExtIO.log 2016-03-11 11:56:15 (notepad++.exe:5708) === start === 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:15 (notepad++.exe:5708) IconOverlayBase::QueryInterface 2016-03-11 11:56:39 (notepad++.exe:5708) ==== end ==== 2016-03-11 11:56:40 (Explorer.EXE:1432) ShellDoneOverlayIcon C:\Users\PC\AppData\Roaming\BitTorrent Sync\ShellExtIO.log 2016-03-11 11:57:09 (notepad++.exe:3148) === start === 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 11:57:09 (notepad++.exe:3148) IconOverlayBase::QueryInterface 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon C:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon K:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon L:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon M:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon N:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon O:\ 2016-03-11 12:04:34 (Explorer.EXE:1520) ShellDoneOverlayIcon R:\ 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface 2016-03-11 12:12:25 (firefox.exe:5344) IconOverlayBase::QueryInterface
  15. KawateTadako

    Frequent and long indexing stressing HDD & CPU

    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.