Description of problem:

Even after all locks (both blocked and active locks) on the ping_pong file are cleared, ping_pong application doesn't exit but hangs on the fuse mounts. 

Before the clear-locks, the replace-brick operation was also initiated. 

Version-Release number of selected component (if applicable):
3.3.0qa33

How reproducible:
often

Steps to Reproduce:
1.create a distribute-replicate volume(3x3).
2.set auth.allow option to <ip_address_of_client)

[04/06/12 - 21:57:30 root@APP-SERVER1 ~]# gluster volume info
 
Volume Name: dstore
Type: Distributed-Replicate
Volume ID: f69cd573-751f-45dd-b741-4bb9caa7cffc
Status: Started
Number of Bricks: 3 x 3 = 9
Transport-type: tcp
Bricks:
Brick1: 192.168.2.35:/export1/dstore1
Brick2: 192.168.2.36:/export1/dstore1
Brick3: 192.168.2.37:/export1/dstore1
Brick4: 192.168.2.35:/export2/dstore1
Brick5: 192.168.2.36:/export2/dstore1
Brick6: 192.168.2.37:/export2/dstore1
Brick7: 192.168.2.35:/export1/dstore2
Brick8: 192.168.2.36:/export1/dstore2
Brick9: 192.168.2.37:/export1/dstore2
Options Reconfigured:
auth.allow: 192.168.2.34

3.create 1 fuse mount from a machine.

4.start 4-5 instances of ping_pong from the same mount ("/usr/sbin/ping_pong ping_pong_file -rw 100 50 300")

5.gluster volume statedump <volume_name>. check if there are blocked locks on ping_pong file

6.while there are blocked locks on ping_pong file execute:
"gluster volume replace-brick <volume_name> <old_brick> <new_brick> start" 
(select the brick which has ping_pong file to replace)

7.gluster volume clear-locks <volume_name> /ping_pong_file kind blocked inode

8.gluster volume replace-brick <volume_name> <old_brick> <new_brick> commit

9.gluster volume clear-locks <volume_name> /ping_pong_file kind blocked posix

10.gluster volume clear-locks  <volume_name> /ping_pong_file kind all posix