AnsweredAssumed Answered

File Timestamp is incorrect, when MapRFS is mounted by DirectNFS

Question asked by tsubo0423 on Aug 6, 2015
- When MapRFS is mounted by DirectNFS, the timestamp is incorrect.

For example:

-- case1: On regular file system (correct)
<pre>
$ cd /tmp
$ echo $(date +%H:%M:%S.%N); touch foo; echo $(date +%H:%M:%S.%N);
10:49:23.129678844
10:49:23.133207639
$ stat foo
  File: 'foo'
  Size: 0               Blocks: 0          IO Block: 4096
Device: 803h/2051d      Inode: 5898267     Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 5000/    mapr)   Gid: ( 5000/    mapr)
Access: 2015-06-05 10:49:23.130417436 +0900
Modify: 2015-06-05 10:49:23.130417436 +0900
Change: 2015-06-05 10:49:23.130417436 +0900
</pre>
The file was created between **10:49:23.129678844** and **10:49:23.133207639**. And, the timestamp is **10:49:23.130417436** (correct).

-- case2: On MapRFS mounted by NFS (incorrect)
<pre>
$ cd /mnt/mapr
$ echo $(date +%H:%M:%S.%N); touch foo; echo $(date +%H:%M:%S.%N);
10:49:55.152786344
10:49:55.161606680
$ stat foo
  File: 'foo'
  Size: 0               Blocks: 0          IO Block: 8192
Device: 1bh/27d Inode: 74211168    Links: 1
Access: (0664/-rw-rw-r--)  Uid: ( 5000/    mapr)   Gid: ( 5000/    mapr)
Access: 2015-06-05 10:49:55.000000000 +0900
Modify: 2015-06-05 10:49:55.001594000 +0900
Change: 2015-06-05 10:49:55.001575000 +0900
</pre>
The file was created between **10:49:55.152786344** and **10:49:55.161606680**. But, the timestamp is **10:49:55.001594000** (incorrect).
I guess it is problem that mili-second number is shifted 2 digits to right direction.

Outcomes