Description of problem: ============ While file is self healing append to the file hangs Version-Release number of selected component (if applicable): ========= glusterfs-server-3.7.5-6 How reproducible: Steps to Reproduce: ============= 1. Create 1x2 volume and mount it on client using fuse 2. Bring down one of the brick and create a big file 2 GB 3. Bring back the down brick and while self heal is going on try to append it to the file but it hangs untill self heal completes Actual results: Expected results: =========== Append to the file should complete without hangs Additional info:
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
QATP: ==== TC#1:data heal 1)create a replica volume may be 1x2 2)Mount volume and create a file of say 1GB 3)now bring down one brick and write more data to the file say 10GB, 4)Now bring back the brick online and once the self heal triggers, keep appending data to the file Expected result: Append must not hang TC#2:with entry heal 1)create a replica volume may be 1x2 2)bring down one brick and create a file of say 5GB 3)Now bring back the brick online and once the self heal triggers, keep appending data to the file Expected result: Append must not hang and entry heal must pass without any issues
QA Result: ============ ran above cases on fuse mount and nfs mount and both passed. hence moving bug to passed and verified [root@dhcp35-191 glusterfs]# rpm -qa|grep gluster glusterfs-client-xlators-3.7.9-2.el7rhgs.x86_64 glusterfs-server-3.7.9-2.el7rhgs.x86_64 python-gluster-3.7.5-19.el7rhgs.noarch gluster-nagios-addons-0.2.5-1.el7rhgs.x86_64 vdsm-gluster-4.16.30-1.3.el7rhgs.noarch glusterfs-3.7.9-2.el7rhgs.x86_64 glusterfs-api-3.7.9-2.el7rhgs.x86_64 glusterfs-cli-3.7.9-2.el7rhgs.x86_64 glusterfs-geo-replication-3.7.9-2.el7rhgs.x86_64 gluster-nagios-common-0.2.3-1.el7rhgs.noarch glusterfs-libs-3.7.9-2.el7rhgs.x86_64 glusterfs-fuse-3.7.9-2.el7rhgs.x86_64 glusterfs-rdma-3.7.9-2.el7rhgs.x86_64
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://access.redhat.com/errata/RHBA-2016:1240