Bug 1624724

Summary:	ctime: Enable ctime feature by default and also improve usability by providing single option to enable
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	ctime	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, nchilaka, pasik, rgowdapp
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-25 16:30:33 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 Kotresh HR 2018-09-03 07:23:18 UTC

Description of problem:
ctime featuers uses client side utime xlator and posix ctime option.
So enabling this feature requires two options to be enabled. It's convenient to make it single options from cli.

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

How reproducible:
Always

Steps to Reproduce:
To enable ctime feature following two cmds needs to be run
1. gluster vol set <volname> features.utime on
2.  gluster vol set <volname> features.ctime on

Actual results:
Need to enable utime and ctime option to enable ctime feature

Expected results:
Good to have only one option 'ctime' to enable ctime feature

Additional info:

Comment 1 Worker Ant 2018-09-03 07:26:46 UTC

REVIEW: https://review.gluster.org/21060 (glusterd/ctime: Use single key for both options) posted (#1) for review on master by Kotresh HR

Comment 2 Worker Ant 2018-11-11 15:44:15 UTC

REVIEW: https://review.gluster.org/21060 (ctime: Enable ctime feature by default) posted (#6) for review on master by Atin Mukherjee

Comment 3 Shyamsundar 2019-03-25 16:30:33 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-6.0, please open a new bug report.

glusterfs-6.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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/