[Bugs] [Bug 1436673] Restore atime/ mtime for symlinks and other non-regular files.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1436673

Vijay Avuthu <vavuthu at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ravishankar at redhat.com
              Flags|                            |needinfo?(ravishankar at redha
                   |                            |t.com)



--- Comment #8 from Vijay Avuthu <vavuthu at redhat.com> ---
Update:
========

Build used: glusterfs-3.12.2-8.el7rhgs.x86_64


Scenario :

1) create 2 * 3 volume and start 
2) kill one of the brick ( N1:b0 )
3) create dirs, file, soft link, hard link and char files.
4) wait for few minutes and modify/append some files and create files inside
some dirs 
4) wait for few min
5) go to node where brick is up ( in the same replica set )
6) "ls -lrt" on the data and note down the timings
7) bringup the brick
9) After healing , from the node where brick was brough down previously ( step
2 ) do "ls -lrt" on the data 
10) compare the atime/mtime from step 6 and step 9

Observation :

All the files, soft links, hardlinks and char files restored the time but only
below dir is not restored the time.


>From N1:

drwxr-xr-x. 2 root root    47 Apr 24 09:01 dir1
drwxr-xr-x. 2 root root    47 Apr 24 09:01 dir2


>From N2:

drwxr-xr-x. 2 root root    47 Apr 24 08:36 dir1
drwxr-xr-x. 2 root root    47 Apr 24 08:36 dir2

> attribute for N2

# getfattr -d -m . -e hex 
/bricks/brick0/testvol_distributed-replicated_brick1/dir1
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick0/testvol_distributed-replicated_brick1/dir1
security.selinux=0x73797374656d5f753a6f626a6563745f723a676c7573746572645f627269636b5f743a733000
trusted.afr.23-client-0=0x000000000000000000000000
trusted.afr.dirty=0x000000000000000000000000
trusted.gfid=0x342afbb2ce814094895409deed35465d
trusted.glusterfs.dht=0x00000000000000007fffffffffffffff
trusted.glusterfs.dht.mds=0x00000000

# 

> scenario for that dir is , kill b0 and create dir from client and touch a empty file inside dir and after 5 min brought up b0.

Placing Needinfo to check the above behavior

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=Cgq3VhoBFQ&a=cc_unsubscribe