Description of problem:
======================

Had a 6node cluster, with a 1*3 volume 'ozone' created on node1, node2 and node3. The setup was brickmux enabled, and the volume option was set to group 'gluster-block'

There were quite a few (<10) blocks created while verifying bz 1514344 and bz 1545049. Started deleting the blocks one by one, and the 'gluster-block delete' command timed out for block 'ob10'. Unable to see anything amiss in the logs /var/log/gluster-block or in /var/log/messages, rebooted all the services, and tried it another time. This time the command succeeded for few blocks and again timed out for block 'ob9'. 

Trying to relate the similarity between the two blocks that timed out, they are of fairly large sizes - 1E and 1P. 
The entire system slows down after the command fails, I suppose because internally it keeps trying to do what was intended, and is not able to get through.. In other words, every 'gluster-block' command given after the failure takes a 2-3 mins to show the output. Restarting the gluster-block daemon does get the system back to normal. 

I was not able to gather much from the logs, maybe we need better logging there..

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.12.2-7
tcmu-runner-1.2.0-18
gluster-block-0.2.1-17


How reproducible:
================
3:3


Steps to Reproduce:
==================
1. Create a block of 1K, 1M, 1G, 1T, 1P, 1E on a replica 3 volume
2. Execute 'gluster-block' delete on all the above created blocks


Actual results:
==============
Block delete succeeds for blocks of sizes 1K, 1M, 1G, 1T, but times out on 1P and 1E.


Expected results:
================
Either block delete should succeed immediately, or it should disallow creation of such large blocks if it affects the functionality. 



Additional info:
===============
Sosreports and gluster-block logs will be copied at http://rhsqe-repo.lab.eng.blr.redhat.com/sosreports/swetas/<bugnumber>