Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dynamite Monkey]

Hi all,

I have a DNS-323 running firmware 1.08.  It's configured with two Seagate 1.5TB drives in RAID 1.

I'm running an online file sync utility that monitors for changes and pushes out the latest version of a file to/from any of four systems including the DNS-323. 

It works excellently other than occasionally, some files that get copied to the DNS-323 have the timestamp off by one second.  This shows up as an exception because the sync utility detects this file as different than the original copy.  Out of about 22,000 files, over 500 had this problem and it is ongoing.  Out of about 200 files that were updated earlier today, 4 of them had this issue.   

I have found other instances of this issue on this forum:  http://forums.dlink.com/index.php?topic=3127.msg16926#msg16926

Any ideas?  I'm guessing this is some rounding issue or NTFS <--> EXT3 issue but would appreciate any insight.  I did reformat the drives after moving to 1.08.

Thanks in advance...

[Biscotte]

Not a solution but an observation

I had this problem.  Much of it relates to the dud time setting on the DNS323.
I have the same thing.  I do a fresh copy across from win machine to dns disc, then compare with a compare programme.  That tells me i need to backup as they are different.  Clearly they are not.   

However I read somewhere in my research that linux only time stamps to within two seconds of correct time whereas windoze is well under a second.

Dunno what sync facility you are using. 
Programmes like vice versa allow for these small time changes - recognises them as the self same file, and there is even a button for one hour difference (allows for different machines timestamping same data - on different summer time clock change)

Biscotte

[jamieburchell]

This is because NTFS timestamps have a greater granularity than EXT file systems. In robocopy for example, you need to specify the /FFT (assume FAT File System - allow for 2 second or less difference) switch to stop this problem. FAT also has a less accurate timestamp than NTFS.

FAT - 2 seconds
exFAT - 10 milliseconds
NTFS - 100 nanoseconds
EXT2/3 - 1 second

[scaramanga]

I just started experimenting with backing-up a PC (NTFS) to the DNS-323 (ext3) using rsync. This issue is addressed by rsync's --modify-window command-line switch.

This FAQ has the details along with some other cross-FS problems, such as UTF8 file names: http://samba.anu.edu.au/rsync/FAQ.html
...and there's the rsync man page: http://samba.anu.edu.au/ftp/rsync/rsync.html