denis4inet

Employees
  • Posts

    34
  • Joined

  • Last visited

Posts posted by denis4inet

  1. VFXLegion,

    BitTorrent Sync open all files in shared mode (ShareMode: FILE_SHARE_READ | FILE_SHARE_WRITE | FILE_SHARE_DELETE), doesn't lock files. But, VFX compositing program open file in non-shared mode, when BtSync open file in shared mode (IMHO). This cause an ERROR_SHARING_VIOLATION in VFX program.

     

    From msdn: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363858%28v=vs.85%29.aspx

     

    wShareMode [in]

    The requested sharing mode of the file or device, which can be read, write, both, delete, all of these, or none (refer to the following table). Access requests to attributes or extended attributes are not affected by this flag.

    If this parameter is zero and CreateFile succeeds, the file or device cannot be shared and cannot be opened again until the handle to the file or device is closed. For more information, see the Remarks section.

    You cannot request a sharing mode that conflicts with the access mode that is specified in an existing request that has an open handle. CreateFile would fail and the GetLastError function would return ERROR_SHARING_VIOLATION.

     

    You can test it using Procmon.exe utility with Path a filter (set to you shared folder).

  2. Hi everyone! 

     
    I have analyzed represented logs.
    The error message was issued by file name encoding error on linux (RPi).

    1. You can check file names on valid UTF8. 

    You need iconv tool.

    # cd <shared_folder_path># ls -R | iconv -f utf8 | grep illegal --color=auto

    If you see message:

    iconv: illegal input sequence at position

     

    that mean in your file tree exists files with non-valid file names.

    2. Or you can wait new releases in which this bug will be fixed.

    Thanks.

  3. Step 1. Turn on Debug Logging. 
    Windows and Mac: click on SyncApp icon and select "Enable Debug Logging". 
    Linux: create file debug.txt with contents of FFFF in the .sync folder. You can find the .sync folder in the same directory where the btsync binary is located.

    Step 2. Reproduce issue 
    Please let Sync collect logs for at least 15 minutes to get enough information.

    Step 3. Attach log file 
    Linux: ./sync/sync.log