Description of problem:
With ctime feature enabled, the first lookup on the file is not healing the gfid if it's not present.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create dist-rep gluster volume (1*2) and mount at /mnt
2. Enable ctime feature
gluster vol set <vol> utime on
gluster vol set <vol> ctime on
3. Create a file on both replica brick in the backend (say file)
4. stat /mnt/file
The first stat is giving ENOENT and is not healing gfid
The first stat should heal the gfid
REVIEW: https://review.gluster.org/20052 (posix/ctime: Fix gfid heal on first lookup) posted (#1) for review on master by Kotresh HR
COMMIT: https://review.gluster.org/20052 committed in master by "Amar Tumballi" <email@example.com> with a commit message- posix/ctime: Fix gfid heal on first lookup
With ctime feature enabled, the gfid is
not healing on first lookup. The fresh
file logic depends on ctime and it was
fetching from backend instead of xattr
with ctime feature enabled. Fixed the
Also fixed a possible hang with inode lock
Signed-off-by: Kotresh HR <firstname.lastname@example.org>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.