Description of problem:

ping_pong starts throwing error when two sessions of ping_pong are started on same file


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

How reproducible:
always

Steps to Reproduce:
1. create a distribute replicate volume
2. start ping_pong test on the nfs mount
3. start another ping_pong test on the same file

another trial with two mounts for the same volume and then trying the ping_pong 
  
Actual results:
the ping pong test starts throwing error
and in second trial with different mounts, but pingpong on same file then both tests were hung


Expected results:
the ping_pong starts putting locks , but if one more session is started the number of locks put per second becomes lower


Additional info:

first scenario, display messages from pingpong

lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided
lock at 0 failed! - Resource deadlock avoided


nfs logs,


[2012-03-08 07:47:41.668219] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.668896] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.670558] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.671543] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.672086] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.672318] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list:
[2012-03-08 07:47:41.672435] W [fd-lk.c:428:print_lock_list] 0-fd-lk: lock list: