Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1753994

Summary:	Mtime is not updated on setting it to older date online when sharding enabled
Product:	[Community] GlusterFS	Reporter:	Sergey Pleshkov <s.pleshkov>
Component:	core	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5	CC:	bugs, pasik
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 12:15:27 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 Sergey Pleshkov 2019-09-20 13:25:29 UTC

Description of problem:
Mtime is not updated on setting it to older date when sharding enabled

Version-Release number of selected component (if applicable):
# gluster --version (RHEL7 and Centos7 two clusters)
glusterfs 5.5

RHEL7 | RHEL6 clients - glusterfs 3.13 / glusterfs 6.5

How reproducible:

Steps to Reproduce:
1. Create 3-way replicated volume.
2. gluster volume set %VOL features.shard on
3. gluster volume set %VOL features.shard-block-size 64MB
4. Mount volume on client by command mount -t glusterfs -oacl %IP:%VOL /%mountpoint
5. touch %mountpoint/file
6. stat %mountpoint/file
7. touch -m -t %older_date_than_created %mountpoint/file

mtime is shown changed after remount volume

Actual results:
mtime for %mountpoint/file was not changed to %older_date_than_created online

Expected results:
mtime for %mountpoint/file will changed to %older_date_than_created online

Additional info:

Comment 1 Sergey Pleshkov 2019-10-28 11:09:23 UTC

Hello everyone.

Will anyone deal with this problem? Are there any workarounds to install older mtime with sharding option?

Comment 2 Worker Ant 2020-03-12 12:15:27 UTC

This bug is moved to https://github.com/gluster/glusterfs/issues/853, and will be tracked there from now on. Visit GitHub issues URL for further details