Bug 1746145 - CentOs 6 GlusterFS client creates files with time 01/01/1970
Summary: CentOs 6 GlusterFS client creates files with time 01/01/1970
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: ctime
Version: 7
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On: 1726175 1743652
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-27 18:27 UTC by Kotresh HR
Modified: 2019-08-28 05:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1743652
Environment:
Last Closed: 2019-08-28 05:50:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 23315 0 None Merged ctime: Fix incorrect realtime passed to frame->root->ctime 2019-08-28 05:50:06 UTC

Description Kotresh HR 2019-08-27 18:27:11 UTC
+++ This bug was initially created as a clone of Bug #1743652 +++

+++ This bug was initially created as a clone of Bug #1726175 +++

Description of problem:
CentOs 6 gluster client with glusterfs volume mounted creates files with time creation "01/01/1970". Files created by user apache, or with user root with vim, or nano, are created with bad date. But if create with touch, the date is correct. 

Version-Release number of selected component (if applicable):
glusterfs-fuse-6.3-1.el6.x86_64

How reproducible:
Create file in mountpoint with vim, or nano.

Steps to Reproduce:
1. yum install centos-release-gluster6
2. yum install glusterfs-client
3. mount -t glusterfs IP:/remotevol /mnt/localdir
4. cd /mnt/localdir
5. vim asdasdad
6. :wq!
7. ls -lah asdasdad


Actual results:
-rw-r--r--    1 root   root      0 ene  1  1970 test

Expected results:
-rw-r--r--    1 root   root      0 jul  1  2019 test

--- Additional comment from baoboa on 2019-07-02 15:23:52 UTC ---

same behavior for a centos6 client

server:
glusterfs-server.x86_64                       6.3-1.el7                       @centos-gluster6

client:
glusterfs-fuse.x86_64                            6.3-1.el6                    @centos-gluster6
kernel version: 2.6.32-573.3.1.el6.x86_64

mount -t glusterfs server:myvol /mnt/myvol

touch /mnt/myvol/test  -> correct time
-rw-r--r-- 1 root root 12 Jul  1 11:59 test

vi /mnt/myvol/test2  -> wrong time (1970)
-rw-r--r-- 1 root root  7 Dec 18  1970 test2

REM: this not the case for a centos7 client, the creation time is correct

recover correct time if ctime is deactivated

"gluster volume set myvol features.ctime off"

ls /mnt/myvol/
-rw-r--r-- 1 root root  7 Jul  2 17:16 test2
-rw-r--r-- 1 root root 12 Jul  1 11:59 test

https://review.gluster.org/#/c/glusterfs/+/22651/ this review look related to this bug/regression

--- Additional comment from  on 2019-07-16 08:38:30 UTC ---

Thanks baoboa,

I can confirm the value "gluster volume set myvol features.ctime off" fix the issue with the date.

Thanks.

--- Additional comment from Worker Ant on 2019-08-20 10:41:20 UTC ---

REVIEW: https://review.gluster.org/23274 (ctime: Fix incorrect realtime passed to frame->root->ctime) posted (#1) for review on master by Kotresh HR

--- Additional comment from Worker Ant on 2019-08-20 11:45:45 UTC ---

REVIEW: https://review.gluster.org/23274 (ctime: Fix incorrect realtime passed to frame->root->ctime) posted (#2) for review on master by Kotresh HR

--- Additional comment from Worker Ant on 2019-08-22 05:35:53 UTC ---

REVIEW: https://review.gluster.org/23274 (ctime: Fix incorrect realtime passed to frame->root->ctime) merged (#3) on master by Amar Tumballi

Comment 1 Worker Ant 2019-08-27 18:29:33 UTC
REVIEW: https://review.gluster.org/23315 (ctime: Fix incorrect realtime passed to frame->root->ctime) posted (#1) for review on release-7 by Kotresh HR

Comment 2 Worker Ant 2019-08-28 05:50:07 UTC
REVIEW: https://review.gluster.org/23315 (ctime: Fix incorrect realtime passed to frame->root->ctime) merged (#2) on release-7 by Rinku Kothiya


Note You need to log in before you can comment on or make changes to this bug.