Description of problem: - writing files to the glusterfs volume. - timestamps of brick1 and brick2 is not the same. Version-Release number of selected component (if applicable): glusterfs-3.3.1-1.el5 (from glusterfs-epel) How reproducible: always Steps to Reproduce: 1. date 06171200. make difference of clock between host1 and host2. 2. touch /path/to/glusterfs/volume/foo. this is no problem. 3. dd if=/dev/zero of=/path/to/glusterfs/volume/foo bs=1024 count=1024. timestamps of host1:/path/to/brick/foo and host2:/path/to/brick/foo is not the same. Actual results: timestamps is not the same. Expected results: timestamps is the same. Additional info:
gigahoge001, Could you tell us if you are still seeing this issue? Could you provide output of the following, gluster volume info <VOLNAME> gluster volume status <VOLNAME> when you observe the issue? It would also help to provide all the GlusterFS log files. This can be found at $INSTALL_PREFIX/var/log/glusterfs/.
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug. If there has been no update before 9 December 2014, this bug will get automatocally closed.
This bug has been CLOSED, and there has not been a response to the requested NEEDINFO in more than 4 weeks. The NEEDINFO flag is now getting cleared so that our Bugzilla household is getting more in order.