Bug 974886

Summary:	timestamps of brick1 and brick2 is not the same.
Product:	[Community] GlusterFS	Reporter:	gigahoge0001
Component:	fuse	Assignee:	bugs <bugs>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3.1	CC:	bugs, gigahoge0001, gluster-bugs, kparthas
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:31 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description gigahoge0001 2013-06-17 03:07:16 UTC

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:

Comment 1 krishnan parthasarathi 2014-07-16 10:51:51 UTC

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/.

Comment 2 Niels de Vos 2014-11-27 14:54:30 UTC

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.

Comment 3 Niels de Vos 2015-05-26 12:33:35 UTC

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.