Re: Wrong atime on recent kernels

[john stultz <johnstul@us.ibm.com>]

On Thu, 2009-12-17 at 12:04 +0100, Petr Titěra wrote:
> Now when I'm looking through stat /stats.file I was able to find some 
> really old instances of this error from October:
> 
>   File: `/mnt/data/linux-2.6/.git/refs/remotes/origin'
>   Size: 4096            Blocks: 8          IO Block: 4096   directory
> Device: fe00h/65024d    Inode: 130953      Links: 2
> Access: (0775/drwxrwxr-x)  Uid: (    0/    root)   Gid: (    0/    root)
> Access: 2009-12-16 21:21:52.776000002 +0100
> Modify: 2009-10-14 07:57:03.1000000000 +0200
> Change: 2009-10-14 07:57:03.1000000000 +0200
>   File: `/mnt/data/linux-2.6/.git/refs/remotes/origin/master'
>   Size: 41              Blocks: 8          IO Block: 4096   regular file
> Device: fe00h/65024d    Inode: 147522      Links: 1
> Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
> Access: 2009-10-14 07:57:04.040000000 +0200
> Modify: 2009-10-14 07:57:03.970000000 +0200
> Change: 2009-10-14 07:57:03.1000000000 +0200
> 
> So this happened before but only recently it started to happen in places 
> where it hurts. I found this trange behaviour because I was unable to 
> create initramfs of new kernels. mkinitrd command could not copy files 
> and preserve their times because of timestamp validity check in cp.

Huh. If its really the case, then its not the change I suspect. 

Ted: Have you seen anything like this? Where the sub-second field holds
a full second of time?


> I will try to revert commit you told me and will test.

Thanks, that will help greatly narrow this down.

thanks again
-john