After the daylight savings time change a few weeks back I noticed something odd on the drives I have mapped to a NetApp.
On a weekly basis (or so) I like to synchronize my home directory on the NetApp with a copy I keep on my home computer. I have been using a shareware program called "FileSync" which compares two directory trees based on file name, size, and date. There is also a option to do a binary compare (takes much longer, obviously).
So, on to the problem: After the time change from EST to EDT, all of the files on the NetApp are exactly one hour older than on my home computer. Based on a little experimentation I did on the PC, I found that when the option to adjust for daylight savings time is disable on the Windows NT machine, all time appearances on the files (including the ones on filer) change by 1 hour. A article on the MSKB states that NT stores all file times in GMT, and converts the display based on the time zone setting on the PC.
I am told that the NetApp stores this information in a UNIX format where it is a 32-bit integer which is "the number of seconds since Jan 1, 1970"
I would suspect that CIFS converts this to GMT for compliance with Windows based on the time zone setting. It would seem there is a error in this conversion where the GMT on the file changes with the Time Zone setting (EST vs EDT). The calculation for GMT should be such that no matter what your time zone setting (even if you move your filer from EST to PST) the stamp on the file should remain constant.
So, is this a bug? or some specific problem I am having?
Thanks, Marc