Hi Steven,
thanks for your hint. I found the file and touched it. Let's see if the problem is solved. When running "ls" on that file the time was shown correctly.
Best Regards
Jochen
-----Original Message----- From: Stephen C. Losen [mailto:scl@sasha.acc.Virginia.EDU] Sent: Wednesday, April 09, 2008 1:24 PM To: Willeke, Jochen Cc: toasters@mathworks.com Subject: Re: nfsd.invalid.nsec.time
Hello toasters,
since some time we do see strange error messages in the logs of one filer.
Here is the message: [nafiler: nfsd.invalid.nsec.time:warning]: Client 192.168.139.43 has
an
invalid nsec mtime (V3):2196581216 on inode:700615
The client is a SLES10 SP1 and has the kernel 2.6.16.46-0.12-smp. I
have
searched NOW and the web but did not find a proper explanation of what is causing this error messages :(
We do see this message only for that client, never seen it for any
other
system.
Best Regards
Jochen
Looks like you have a file with an invalid modification time (mtime) timestamp. The timestamp 2196581216 displays as July 4, 1903 on my system (obviously negative). The inode gives you a clue which file. You can use the Unix "find" command to find it:
find dirname -inum 700615 -ls
Perhaps if you "touch" this file to change the timestamp, then the problem will go away. Also, is the clock set properly on the NFS client?
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support