On 01/17/13 02:32, Dmitry Gutov wrote:
dired.c:958: stat_mtime=1358412092.606214085
modify again
fileio.c:5414: stat_mtime=1358412092.606214000
The first time stamp comes from lstat, the second
from stat. If the file is actually on an NTFS file
system from the underlying host, the first time stamp
cannot possibly be right, since these file systems
have a time stamp resolution of 100 nanoseconds.
The second time stamp would be the correct one.
So it does seem to be a file system bug. Is this something
that you can reproduce with a little C program, that
creates a file, and invoke lstat and stat on it?
What happens when you run the following program
in your file system? It should output time stamps
that are identical. You may need to substitute
something else (like sleep (10)) for "sync ()"
to trigger the bug.