Stardust Posted August 1, 2015 Report Share Posted August 1, 2015 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. Quote Link to comment Share on other sites More sharing options...
Helen Posted August 4, 2015 Report Share Posted August 4, 2015 Stardust, What Sync version you use? This was a known bug in older versions of Sync and is fixed by now. Please update your peers from here Quote Link to comment Share on other sites More sharing options...
Stardust Posted August 10, 2015 Author Report Share Posted August 10, 2015 Stardust, What Sync version you use? This was a known bug in older versions of Sync and is fixed by now. Please update your peers from hereUgh, just rechecked. It seems one of the peers was running a version from Jun 12 (2.0.124). That peer was not in use (ie. no updates made locally, but still on r/w sync). I guess this was the problem? Quote Link to comment Share on other sites More sharing options...
Helen Posted August 10, 2015 Report Share Posted August 10, 2015 yes, it was fixed in 2.0.125 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.