Description of problem:
==========================
whenever I create a file using truncate, the file is always set with the access time /atime as epoch time starting

This can be an issue, for applications relying on atime explicitly.
There can be different apps like mail servers, archival tools relying on atime
and due to this we may end up serving wrong time

I am not able to see this on fuse mount
Version-Release number of selected component (if applicable):
=========================
[root@dhcp35-37 3.8.4-11]# rpm -qa|egrep "gluster|ganesha"
glusterfs-events-3.8.4-11.el7rhgs.x86_64
glusterfs-rdma-3.8.4-11.el7rhgs.x86_64
glusterfs-api-3.8.4-11.el7rhgs.x86_64
glusterfs-server-3.8.4-11.el7rhgs.x86_64
nfs-ganesha-gluster-2.4.1-3.el7rhgs.x86_64
nfs-ganesha-debuginfo-2.4.1-3.el7rhgs.x86_64
glusterfs-libs-3.8.4-11.el7rhgs.x86_64
glusterfs-cli-3.8.4-11.el7rhgs.x86_64
nfs-ganesha-2.4.1-3.el7rhgs.x86_64
glusterfs-3.8.4-11.el7rhgs.x86_64
glusterfs-fuse-3.8.4-11.el7rhgs.x86_64
glusterfs-debuginfo-3.8.4-11.el7rhgs.x86_64
glusterfs-client-xlators-3.8.4-11.el7rhgs.x86_64
python-gluster-3.8.4-11.el7rhgs.noarch
glusterfs-ganesha-3.8.4-11.el7rhgs.x86_64
glusterfs-geo-replication-3.8.4-11.el7rhgs.x86_64




How reproducible:
=======
always


Steps to Reproduce:
1.created a dist=ec volume on a 6 node cluster and 4 node ganesha
2.mounted the volume on two clients with different vips
3.now issue a truncate of file say "truncate file1 --size 4gb"

if u check the atime, it always shows it as below

[root@dhcp35-107 disperse-ganesha]# stat gyan
  File: `gyan'
  Size: 4000000000	Blocks: 0          IO Block: 1048576 regular file
Device: 1ch/28d	Inode: 11298515324991194880  Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 1970-01-01 05:30:00.000000000 +0530
Modify: 2017-01-09 15:46:36.000000000 +0530
Change: 2017-01-09 15:46:36.000000000 +0530