Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a server with an NFS mounted volume.

When I create a file on a local volume, the time stamp matches the date command.

When I create a file on the NFS mounted volume, the time stamp is off. The time on the NFS server is correct, but the timezone is EDT - one hour different.

# date
Tue Oct 1 15:13:08 ADT 2013

# cd /path/to/local/volume
# touch local
# ls -la local
-rw-r--r-- 1 root root 0 Oct 1 15:13 local

# cd /path/to/nfs/mount
# touch nfs
# ls -la nfs
-rw-r--r-- 1 root root 0 Oct 1 12:49 nfs
share|improve this question

The mounted volume is not actually on your system. When you create a file on it, it is actually the remote OS that is doing the creating. Therefore, what you're seeing is probably the remote system's time which is not the same as your own.

If you have ssh access to the machine that exports the NFS volume, you can check by loggin in and running date there.

share|improve this answer
I guess my note about the NFS server having the correct time isn't clear. I logged into the server, and the time is the same, except that it is running a different time zone. The file "nfs" file in the question should then have a timestamp of 14:13, or at least something :13, but it appears to be off by more than an hour. – chris Oct 2 '13 at 19:05
@chris ah, OK. Could you please edit your question to add the output of date on both machines? That should clarify things. Also mention the OS of both machines as well as the filesystem of the nfs volume. If you have ssh access to the machine in question also try creating a file on the exported volume when actually logged in to the machine. Does that make a difference? – terdon Oct 2 '13 at 19:39

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .