Created attachment 1034179[details]
statedump of the process
Description of problem:
=======================
Created 1x(8+4) disperse volume. Fuse mounted on the client and started linux untar. Brough down 2 of the bricks and after some time brought them up with volume start force. Linux untar on the client hangs
Version-Release number of selected component (if applicable):
============================================================
[root@transformers ~]# gluster --version
glusterfs 3.7.0 built on Jun 1 2015 07:14:51
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[root@transformers ~]#
How reproducible:
=================
100%
Steps to Reproduce:
===================
As in description
Actual results:
===============
linux untar hangs
Expected results:
================
no hangs
Additional info:
================
volume info
============
[root@transformers ~]# gluster v info vol1
Volume Name: vol1
Type: Disperse
Volume ID: e7e43939-3d7e-4052-8242-2067cd803d7f
Status: Started
Number of Bricks: 1 x (8 + 4) = 12
Transport-type: tcp
Bricks:
Brick1: interstellar:/rhs/brick1/vol1
Brick2: transformers:/rhs/brick1/vol1
Brick3: ninja:/rhs/brick1/vol1
Brick4: interstellar:/rhs/brick2/vol1
Brick5: transformers:/rhs/brick2/vol1
Brick6: ninja:/rhs/brick2/vol1
Brick7: interstellar:/rhs/brick3/vol1
Brick8: transformers:/rhs/brick3/vol1
Brick9: ninja:/rhs/brick3/vol1
Brick10: interstellar:/rhs/brick4/vol1
Brick11: transformers:/rhs/brick4/vol1
Brick12: ninja:/rhs/brick4/vol1
Options Reconfigured:
performance.readdir-ahead: off
features.uss: off
features.quota: off
features.inode-quota: off
client.event-threads: 2
server.event-threads: 2
cluster.disperse-self-heal-daemon: enable
[root@transformers ~]#
statedump of the process will be attached.
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-2015-1495.html