Description of problem: ======================== One of the VM moved into the paused state when a brick was killed in 1*2 replica setup. Client logged a message "[2013-06-06 06:25:48.558426] W [fuse-bridge.c:665:fuse_attr_cbk] 0-glusterfs-fuse: 4772448: FSTAT() /cf5fb27d-5ee7-4e59-818f-4927abfbaff6/images/1493c50e-50c6-4f9b-9af4-11db021721c4/1cb0178a-78b4-4a11-b49e-20c8334adf37 => -1 (Transport endpoint is not connected)" Version-Release number of selected component (if applicable): ============================================================= # rpm -qa | grep gluster | grep 3.4.0 glusterfs-fuse-3.4.0.8rhs-1.el6rhs.x86_64 glusterfs-geo-replication-3.4.0.8rhs-1.el6rhs.x86_64 glusterfs-rdma-3.4.0.8rhs-1.el6rhs.x86_64 glusterfs-3.4.0.8rhs-1.el6rhs.x86_64 glusterfs-server-3.4.0.8rhs-1.el6rhs.x86_64 # Steps Carried: ============= 1. Created 1*2 replica setup from two servers 2. Mounted on Client from RHEVM 3. Created and Started 5 VM's (vm1 to vm5) 4. Brought down server1 (poweroff) 5. Created and started two new VM's (vm6,vm7) 6. Created snapshot of existing VM's (VM1 to VM5) 7. Brought back the server1 8. shd completes self heal. 9. Brought down the brick in server2 10. VM moved into the paused state. Actual results: =============== VM moved into the paused state. Expected results: ================= VM should not move into the paused state.
Patch to 873962 fixes this. This bug depends on 873962.
Ran the same test case with build: glusterfs-server-3.4.0.24rhs-1.el6rhs.x86_64 All VM's were Up and Running. Marking the bug 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. http://rhn.redhat.com/errata/RHBA-2013-1262.html