Description of problem:
=======================
Hard link fl3275 is lost when performed below steps,
Version-Release number of selected component (if applicable):
3.8.4-3.el7rhgs.x86_64
How reproducible:
=================
1/1
Steps to Reproduce:
===================
1) Create a distributed replicate volume and start it.
2) Fuse mount the volume on multiple clients.
3) Perform below tasks simultaneously from multiple clients,
a) From client-1, touch --> for i in {1..20000};do touch f$i;done
b) From client-2, create hard links for the created files , for i in {1..20000};do ln f$i fl$i;done
c) From client-3, change the permissions for the created files, for i in {1..20000};do chmod 660 f$i;done
d) From client-4, do a continuous lookup.
5) While the tasks in step-4 are in progress, add few bricks to the volume and start rebalance.
Wait till step-4 and step-5 completes.
Check the created files and hard links count.
Actual results:
===============
Hard link fl3275 is lost
Expected results:
=================
No data loss should be seen.
Repeated the steps in the description thrice with glusterfs version 3.8.4-10.el7rhgs.x86_64. I did not see any hardlink loss, all the created hardlinks are available post rebalance.
Moving this BZ to Verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2017-0486.html
Description of problem: ======================= Hard link fl3275 is lost when performed below steps, Version-Release number of selected component (if applicable): 3.8.4-3.el7rhgs.x86_64 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1) Create a distributed replicate volume and start it. 2) Fuse mount the volume on multiple clients. 3) Perform below tasks simultaneously from multiple clients, a) From client-1, touch --> for i in {1..20000};do touch f$i;done b) From client-2, create hard links for the created files , for i in {1..20000};do ln f$i fl$i;done c) From client-3, change the permissions for the created files, for i in {1..20000};do chmod 660 f$i;done d) From client-4, do a continuous lookup. 5) While the tasks in step-4 are in progress, add few bricks to the volume and start rebalance. Wait till step-4 and step-5 completes. Check the created files and hard links count. Actual results: =============== Hard link fl3275 is lost Expected results: ================= No data loss should be seen.