Search the Community

Showing results for tags 'corrupt'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hi, I have setup a read-sync folder on my android, with selective-sync. I have a library of audiobooks, where each folder contains 100-200 wma or mp3 files. When I sync a folder, all audio-book files are downloaded. Bittorrent-sync states that all files are successfully downloaded. When I view the files in an android explorer, size of file looks ok. But when I try to play in VLC, not all files are playable. When i download 100 files, generally 5-10 files are corrupt. I.e. media player cannot read audio-tag information, or play the file. When I "clear" the corrupt files in bittorrent-sync and re-download them, they are usually ok to play again. I.e. I am confident that files are ok on server, but become corrupt on my Android device while downloading. Why does Bittorrent sync think files are ok? When they actually are not? Is this the root-cause Android platform? Is the root-cause an WMA or mp3 issue? May I encounter the same phenomena on other files as jpg when syncing between NAS-Windows application. I am worried for my picture backups too. I have updated to the latest 2.3.7 version on all server, and downloaded latest android, which is 2.3.5.
  2. A quit search of the forums did not turn up this issue, which is surprising as I've had it happen to my files frequently in the last 6 months or so. Specifically, it appends what appears to be logging information to files at random. An example can be found below. The first part is the real file (a rpm package spec file), but after the %doc line, random garbage appears. This corruption is generated on the host on which the file is altered, and propagates to every other host. <snip> rm $RPM_BUILD_ROOT%{_libdir}/*.la %cleanrm -rf $RPM_BUILD_ROOT %files%defattr(-, root, root)%{_libdir}/*.so.* %files devel%defattr(-, root, root)%{_libdir}/*.so%{_includedir}/meos++/*%doc %{_docdir}/%{name} [20150730 11:30:14.411] SyncFolderNotify: SyncFolderNotify: "0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp", event = "IN_MODIFY"[20150730 11:30:14.411] [OnNotifyFileChange] "/home/nilss/work/HEAD/packages/.sync/0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp"[20150730 11:30:14.411] SyncFolderNotify: SyncFolderNotify: "0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp", event = "IN_MODIFY"[20150730 11:30:14.411] [OnNotifyFileChange] "/home/nilss/work/HEAD/packages/.sync/0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp"[20150730 11:30:14.411] SyncFolderNotify: SyncFolderNotify: "0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp", event = "IN_MODIFY"[20150730 11:30:14.411] [OnNotifyFileChange] "/home/nilss/work/HEAD/packages/.sync/0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp"[20150730 11:30:14.411] SyncFolderNotify: SyncFolderNotify: "0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp", event = "IN_MODIFY"[20150730 11:30:14.411] [OnNotifyFileChange] "/home/nilss/work/HEAD/packages/.sync/0EAD2A2BDFBBDC5EE30141C3051CC4811CE3652C.SyncTemp" <snip> BTW, do you really trigger a sync on IN_MODIFY and not IN_CLOSE_WRITE? That seems exessive... Can someone move this? It seems I've posted it on the wrong part of this forum.