I have an HPC environment and I am running GX10.0.03. I noticed that if I list the contents of a directory the time stamp shows the year the file was created when it should show the hour and minute. This seems to only happen if I list the contents the same minute it is being created. If I wait 30 seconds or so and run it again I can see the time stamp correctly. Is this a NFS "feature" or is it caused by the GX code since I am running stripped aggregates and stripped volumes.
Hello! We have this exact same issue right now and we are trying to figure out a fix as well. I opened up a ticket with NetApp and the engieer we were working with indicated that the server, not the filer, was responsible for putting the time stamp on the file. While we are not sure that is 100% correct, we have continued to look into the issue and have been unable to isolate the skew in time. We have run through all our NTP settings on the servers and the filer as well as looking at another filer (FAS2050 - ONTAP 188.8.131.52) we have in our environment and ironically, the FAS2050 (ONTAP 184.108.40.206) does not have the same issue as our FAS3020(ONTAP 220.127.116.11). Here is what we see on our FAS3020:
<finally a timestamp...but 1 minute AFTER the file was created.
We found this on the NetApp site, but that does not explain why we have all of the LINUX servers with our FAS2050 that are NOT having the issue...we have all the servers with the timestamp issue on the FAS3020...let us know what you found...thanks!!
*Solution ID*: kb29382 *Last updated*: 24 SEP 2008 A Linux host displays the date in the time stamp of files, but the time is omitted *Symptoms* Linux clients display the date in the time stamp after issuing the *ls** *command, but the time is omitted. When the command* ls -latr* is issued on the Linux client, the files appear in the correct order. However, files that have been touched by the client list only the date, while files that have not been read or written are displayed correctly with both date and time information. A Linux host displays the date in the time stamp of files, but the time is omitted. *Cause of this problem* Time is out of sync. *Solution* 1. Ensure that the filer and the client's time and time zone are in sync. 2. Issue a date command to verify the correct date, time and time zone. *Note:* Verify that the proper time zone rules are in effect for all systems (ie. EDT versus EST). 3. Ensure that the proper time zone files are in */etc/**zoneinfo* folder. 4. Issue the* timezone* command with the proper time zone to correct any disparity. 5. Correct time skew issues with the date command. *Related link:* Updating timezone information on NetApp Appliances in the United States <https://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb20094>*Environment* NetApp filer Data ONTAP GX Data ONTAP 7G and earlier
NFS protocol provides for both server-based and client-based time stamps. As far as I can tell, Linux defaults to server-side timestamps without any way to change it (it could depend on kernel version as well).
NFS sends all time/date info to the client in UNIX time (i.e. # of seconds since the epoch). It is entirely up to the client to decide how to display that time. This helps things issue with timezones, etc.