On Thu, Jul 08, 2004 at 12:49:28PM +1200, Mark Davies wrote:
> No the Solaris boxes haven't been touched and its only happening with files on 
> the NFS server thats been updated to 2.0F, not those that are still at 1.6ZH 
> and its happening to quite a lot of files.   (I have occassionally seen that 
> error on Solaris before but thats been for very large files - with holes - 
> which is not the problem here).
> 
> As I discovered in the tail part of my message the actual problem is that 
> something is setting the atime of the file(s) to a very bogus value and its 
> just that Solaris is complaining about that value while NetBSD and Tru64 are 
> happy to use it.   If I "touch" the file on the server the atime comes right 
> and Solaris is happy to access it.

I'll have to check this the next time I see it.
It doesn't happen often here, otherwise the users would have complained :)

> 
> Still leaves the question what is breaking the atime's in the first place?

It's probably something that got pulled up to the 1.6 branch as well.
I never noticed it with 1.6.1_STABLE, before upgrading to 1.6.2.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--