Search the Community

Showing results for tags 'system volume information'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. Hello, Today I installed Bittorrent Sync and tried to share an entire drive. It is not the system drive, but a second drive used for storage of data. After indexing was done, I noticed, that the Recycle Bin was included in the index. I opened .SyncIgnore and saw that the default entries do not specify the following two folders, which are present on all drives in a Windows Vista/7/8 system: Recycle Bin System Volume Information So, I would suggest that the following entries get added to the default .SyncIgnore file: \$RECYCLE.BIN \System Volume Information It may also be a good idea to add the following two files: \pagefile.sys \swapfile.sys The reason is that these two (unlike hiberfil.sys), may be relocated on drives other than C:
  2. Greetings Sync Monkeys, I absolutely LOVE BTsync - great job so far. I created this user to participate in the forum so I can tell you about a problem I have spent a full day on trying to resolve and can not: I am a media creator and have my sound libraries on a 2TB drive. I want to sync these libraries to my laptop so I can easily create music using these libraries on the road. Given the massive size and somewhat dynamic nature of these libraries (I constantly update my sounds), BTsync is PERFECT for what I need. I set up BTsync to syncronize my S: drive on my workstation to my S: drive on my laptop. I did the same with my T: drive (my second set of libraries). To my dismay, on one drive, only a few megabytes of 1.2 terabytes syncronized, and on the other drive *nothing* synchronized. I tried changing permissions, drive ownership, share settings, tried leaving it overnight to sync - all to my dismay. The indexing on the host machine was not at all matching up with what it should have been. Then I discovered how to turn on the debug logging. here is what I found in the error log: New torrent created for file System Volume Information\tracking.log mt:1388884139 DA49A9B09544F1E47F42C5B97919A7EF45CA6550 [2014-01-12 19:49:30.112] SyncFolderScanner: Got error 5 while obtaining file info for \\?\Q:\System Volume Information\ Something was up with the System Volume Information folder (a system folder present on the root of Windows drives). I did some more hunting, and someone had come up with a solution, granting Admin rights to the folder: I tried this solution, but got another error: New torrent created for file System Volume Information\tracking.log mt:1388884139 DA49A9B09544F1E47F42C5B97919A7EF45CA6550 [2014-01-12 19:49:30.112] SyncFolderScanner: Got error 5 while obtaining file info for \\?\Q:\System Volume Information\SPP So, it's the same error, but nested down a level. I wasn't about to changed permissions on 4 drives , nested X levels deep. So, I did some more hunting and found this article: The poster suggested adding the recycle bin and the system volume information folders to the default sync exclusion list. An excellent idea! But the Admin disagreed, saying "I don't think these things shouldn't be added to the default .SyncIgnore file as they are very specific use cases!!" I ahve to say I *completely* disagree. In my case, and in the case of many media creators, syncing an entire drive is paramount. For example, media libraries, client drives, video capture drives etc. I'm not sure if that Admin had a limited understanding of Windows, but it seems to me that calling a root drive sync a "specific use case" is a bit strange! Anyhow, at this point it appears that BTsync will *not* sync properly using the root of a drive. Is there anyone else who would agree? Is this a good feature request? Do you think it reasonable to want to use BTsync in this manner? If so, is there a fix in the works? keep up the AWESOME work, BTsync! MR ------------------ Related posts ------------------
  3. When using BTSync to synchronize volume E:\ I happened to encounter a strange behaviour: After a while new files were not synched although BTSync claimed to have done so. After heavy testing I noticed an even more strange behaviour: Folders alphabetically preceeding the folder 'System Volume Information' were not mentioned when synching neither single files in the root folder. Trying to re-index folder E:\ (remove then re-add the folder) would suddenly lead to consider only a few files instead of thousands being on the volume. Enabling debug logging uncovered the following error: Got error 5 while obtaining file info for \\?\E:\System Volume Information. After encountering this error, BTSync stopped synching (but claimed that synching was sucessfull). The folder 'System Volume Information' was at first not accessible to view its content, I had to add appropriate rights (added it to the group of Administrators). In there I found a file named 'tracking.log'. After the date of the timestamp of that file, BTSync had stopped working properly. When I had given access to 'System Volume Information' folder, BTSync worked properly again. The file 'tracking.log' is created by 'LocalSystemNetworkRestricted' via svchost.exe (One can verify this by using e.g. the Windows 7 resource monitor). It seems to be created in the root folder 'System Volume Information' on every drive. So what exactly happened? BTSync tries to scan every folder (starting alphabetically at the last one), encounters missing access rights on 'System Volume Information'. It then stops working but claims that synchronizing has been done. Solution: Grant access to the folder and BTSync will work properly again. (It does not help to simply exlude that folder in the .SyncIgnore file) Maybe this my observation may help someone.