Chris V Posted July 8, 2013 Report Share Posted July 8, 2013 I can't see anything wrong with the timestamp on this file - what might be causing this error? Should I do anything about it? Would you like an error log?Thanks, Chris(btsync 1.1.27 on Windows 7) Quote Link to comment Share on other sites More sharing options...
sergey@bt Posted July 8, 2013 Report Share Posted July 8, 2013 Currently Sync skips files with modification time set to 0 (Jan 1, 1970). Try to update timestamp (open & save file), it should fix this error. Quote Link to comment Share on other sites More sharing options...
Chris V Posted July 8, 2013 Author Report Share Posted July 8, 2013 Windows reports Created timestamp as 07/08/2011 16:51:01, and Last modified timestamp as 07/08/2011 16:51:03. There doesn't appear to be anything in the log relating to it. Quote Link to comment Share on other sites More sharing options...
Chris V Posted July 10, 2013 Author Report Share Posted July 10, 2013 I have found that the error message is erroneous.While the History tab displays "Skipping file ... with bad timestamp", and the error log contains messages "SyncFilesController: got file with zero modification time, skipping", in fact, the timestamps are fine, but there is some problem with ownership and/or permissions on the files: Windows file properties is giving me errors "To continue, you must be an administrative user with permission to view this object's security properties" and "Unable to display current owner".Perhaps the development team could review this and correct the error message for this case? Quote Link to comment Share on other sites More sharing options...
sergey@bt Posted July 10, 2013 Report Share Posted July 10, 2013 Thanks for details. Indeed Sync may report incorrect timestamp error for files which it's not able to access. We will correct it. Quote Link to comment Share on other sites More sharing options...
Chris V Posted July 10, 2013 Author Report Share Posted July 10, 2013 I'm not sure if it has any bearing, but most (all?) of the affected files seem to be '.mht' files... curious! Quote Link to comment Share on other sites More sharing options...
dfreniche Posted July 26, 2013 Report Share Posted July 26, 2013 Hi allI've found this bug also in Mac. The problem is as stated, that every file with date set to 1 Jan 1970 does not get synced . The message "bad timestamp" is not very helpful here.For example, that's the result of ls:$ ls -al@total 48drwxr-xr-x 7 dfreniche staff 238 31 ago 2012 .drwxr-xr-x 17 dfreniche staff 578 31 ago 2012 ..-rw-r--r--@ 1 dfreniche staff 3892 1 ene 1970 toolkit_gwt.pngcom.dropbox.attributes 162 -rw-r--r--@ 1 dfreniche staff 3675 1 ene 1970 toolkit_swing.pngcom.dropbox.attributes 160 -rw-r--r--@ 1 dfreniche staff 3894 1 ene 1970 toolkit_swt.pngcom.dropbox.attributes 160 -rw-r--r--@ 1 dfreniche staff 4007 1 ene 1970 toolkit_xwt.pngcom.dropbox.attributes 161 -rw-r--r-- 1 dfreniche staff 6455 1 ene 1970 toolkits.xmlAll these are files copied from Dropbox, and I'm showing the special attributes (this is a Mac only feature).The final solution would be to have a setting to allow set the date of those files to the current date. A workaround in the meantime is to create a script that does exactly this. I've written that script, and tested. It's here:https://gist.github.com/dfreniche/6090995Greets! Quote Link to comment Share on other sites More sharing options...
jdrch Posted October 3, 2013 Report Share Posted October 3, 2013 I just noticed this myself. I think I'll switch back to Cubby - which doesn't have this issue - until it's resolved. Quote Link to comment Share on other sites More sharing options...
Harold Feit Posted October 3, 2013 Report Share Posted October 3, 2013 What version of sync are you using? Quote Link to comment Share on other sites More sharing options...
vadimt Posted October 4, 2013 Report Share Posted October 4, 2013 I just noticed this myself. I think I'll switch back to Cubby - which doesn't have this issue - until it's resolved. It will be fixed in 1.2 version.Thanks! Quote Link to comment Share on other sites More sharing options...
blippo Posted October 23, 2013 Report Share Posted October 23, 2013 So, in the furure, all files regardless timestamp the files will be synced? *edit* Im syncing 1 terrabyte of data, wich i cannot edit the timestamp. The files need to exactly as they are on the original drive.. Will this be a problem for me in the future? Thanks for a great software! Quote Link to comment Share on other sites More sharing options...
jdrch Posted November 6, 2013 Report Share Posted November 6, 2013 This seems to have been fixed in the latest release. Thanks guys! Quote Link to comment Share on other sites More sharing options...
johnny1496 Posted November 8, 2013 Report Share Posted November 8, 2013 I ran into a similar problem, running Sync 1.1.82. I had a "doc.kml" file generated from Google Earth. The modified time stamp was in the year 1601, and I got the "bad timestamp" error from Sync. For my purposes I just made a small change to the file and it synced, but I figured I would pass the information along. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted November 9, 2013 Report Share Posted November 9, 2013 I ran into a similar problem, running Sync 1.1.82....For my purposes I just made a small change to the file and it synced, but I figured I would pass the information along.As already indicated earlier in the thread, this issue has now been resolved though for 1.2.x builds of Sync. If you're still running 1.1.82, it's worth updating 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.