[Gluster-users] Different results in setting atime

[David Spisla]

Hello Gluster Community,

I did some experiments with setting the atime in different scenarios. In
scenario 2,3 and 4 I have a simple replica 2 volume with worm-file-level on

1. Setting atime on XFS:












*[davids at gluster-test1 src]$ touch test[davids at gluster-test1 src]$ sudo
touch -a -t 197001010001 test[davids at gluster-test1 src]$ stat test  File:
‘test’  Size: 0             Blocks: 0          IO Block: 4096   regular
empty fileDevice: fd00h/64768d    Inode: 16854052    Links: 1Access:
(0664/-rw-rw-r--)  Uid: ( 1000/  davids)   Gid: ( 1000/  davids)Access:
1970-01-01 00:01:00.000000000 +0100Modify: 2018-01-05 09:06:34.567406414
+0100Change: 2018-01-05 09:10:22.656813779 +0100 Birth: -*













*2. Setting atime from FUSE Mount:[davids at gluster-test1 gluster0]# touch
test[davids at fgluster-test1 gluster0]# sudo touch -a -t 197001010001
test[davids at gluster-test1 gluster0]# stat test  File: ‘test’  Size:
0             Blocks: 0          IO Block: 131072 regular empty fileDevice:
28h/40d    Inode: 11420445633475641741  Links: 1Access: (0644/-rw-r--r--)
Uid: (    0/    root)   Gid: (    0/    root)Access: 2106-02-07
06:29:16.000000000 +0100Modify: 2018-01-05 09:15:28.655599273 +0100Change:
2018-01-05 09:15:48.744780537 +0100 Birth: -*













*3. Setting atime from SMB Client (mount.cifs):[davids at gluster-test1
gluster0]$ touch test[davids at gluster-test1 gluster0]$ sudo touch -a -t
197001010001 test[davids at gluster-test1 gluster0]$ stat test  File: ‘test’
Size: 0             Blocks: 0          IO Block: 16384  regular empty
fileDevice: 27h/39d    Inode: 9521130001639226397  Links: 1Access:
(0644/-rw-r--r--)  Uid: ( 1000/  davids)   Gid: ( 1000/  davids)Access:
2018-01-05 09:18:02.000000000 +0100Modify: 2018-01-05 09:18:02.000000000
+0100Change: 2018-01-05 09:18:01.000000000 +0100 Birth: -*


*So I would expect a behaviour like in scenario 1 for all scenarios. In
scenario 2 the atime is jumping to the year 2106 and in scenario 3 nothing
happens. Now I try this one:*
*4. Setting atime from SMB (mount.cifs) with another value*












*[davids at gluster-test1 gluster0]$ touch test[davids at gluster-test1
gluster0]$ sudo touch -a -t 197001010101 test[davids at gluster-test1
gluster0]$ stat test  File: ‘test’  Size: 0             Blocks: 0
IO Block: 16384  regular empty fileDevice: 27h/39d    Inode:
9521130001639226397  Links: 1Access: (0644/-rw-r--r--)  Uid: ( 1000/
davids)   Gid: ( 1000/  davids)Access: 1970-01-01 01:01:00.000000000
+0100Modify: 2018-01-05 09:18:02.000000000 +0100Change: 2018-01-05
09:23:09.000000000 +0100 Birth: -*


*If I print the atime from inside of the xlator stack, there is the value
of 60 seconds for this. According to scenario 4, gluster is starting to
count the seconds from 1970-01-01 01:00 and not from 00:00. It seems to be
that the first hour in 1970 can not be set as atime. Also scenario 2 is
strange for me. What could be the reason for this? What kind of internal
computing does gluster with the atime?*

*Regards*

*David Spisla *
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180105/aaf566db/attachment.html>