Bug 1580529

Summary:	posix/ctime: Access time is not updated for file with a hardlink
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	posix	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1582072 (view as bug list)		Environment:
Last Closed:	2018-10-23 15:09:43 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:
Bug Depends On:
Bug Blocks:	1582072

Description Kotresh HR 2018-05-21 17:16:03 UTC

Description of problem:
When ctime feature is enabled, access time of file which has hardlink is not changed with the cmd 'touch -a <file>'

Version-Release number of selected component (if applicable):
mainline

How reproducible:
Alwasy

Steps to Reproduce:
1. Creatt gluster volume
2. Enable ctime feature (Both ctime and utime option)
3. Create a file
4. Create a hardlink for above file
5. Record atime by doing stat file
6. touch -a file
7. Record atime and compare with above. 

Actual results:
atime should is not updated

Expected results:
atime should be updated

Additional info:

Comment 1 Worker Ant 2018-05-21 17:25:41 UTC

REVIEW: https://review.gluster.org/20051 (posix/ctime: Fix atime update for hardlink) posted (#1) for review on master by Kotresh HR

Comment 2 Worker Ant 2018-05-24 06:07:01 UTC

COMMIT: https://review.gluster.org/20051 committed in master by "Kotresh HR" <khiremat> with a commit message- posix/ctime: Fix atime update for hardlink

With ctime feature enabled, atime is not
being updated for a hardlink when the file
is accessed.

e.g., touch -a <hardlink_file> fails to
update atime. This patch fixes the same.

fixes: bz#1580529
Change-Id: I2201c88d502d0070300a1f5023af1b36951284ec
Signed-off-by: Kotresh HR <khiremat>

Comment 3 Shyamsundar 2018-10-23 15:09:43 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/